use new getListenerFromPlugin signature

[MayCXC]

this is for when caddyserver/caddy#6651 gets released

[jurekl]

I think that in each of the getXXXListener functions the following correction should be made, otherwise I can't compile the plugin code

...
na, err := caddy.JoinNetworkAddress(network, host, portRange)
...

caddy.JoinNetworkAddress() returns a string, so that's definitely not correct, but it will probably be fine after changing it to:

...
na, err := caddy.ParseNetworkAddress(caddy.JoinNetworkAddress(network, host, portRange))
...

EDIT:
After this change, I can formally build this plugin, but it does not work as it should :
Example error:
Error: loading initial config: loading new config: http app module: start: starting HTTP/3 QUIC listener: tsnet: address invalid AddrPort: missing port in address

Since I am actively using the caddy-tailscale module, I have to revert to the caddy commit from before the ListenerFunc declaration change for now :-(

[jurekl]

Last commit 2 months ago, I wonder if project caddy-tailscale is still active/alive? After the aforementioned significant change in the caddy function declaration, building this plugin in its current form is impossible.
It seemed to me that this plugin has many very satisfied and active users. Meanwhile, after the aforementioned change in caddy, we already have two new caddy tags, the last one 2.9.1.
This PR does not solve the problem I mentioned above, it simply does not compile. I am very curious if in this situation users of this plugin do not update caddy, like me?
Or maybe there is another solution, something I do not know about? I would be happy to use the knowledge/practice/experience of others :-)
Best regards...

[MayCXC]

Last commit 2 months ago, I wonder if project caddy-tailscale is still active/alive? After the aforementioned significant change in the caddy function declaration, building this plugin in its current form is impossible. It seemed to me that this plugin has many very satisfied and active users. Meanwhile, after the aforementioned change in caddy, we already have two new caddy tags, the last one 2.9.1. This PR does not solve the problem I mentioned above, it simply does not compile. I am very curious if in this situation users of this plugin do not update caddy, like me? Or maybe there is another solution, something I do not know about? I would be happy to use the knowledge/practice/experience of others :-) Best regards...

My apologies, and thanks for #89 . The missing ParseNetworkAddress was a git error, but I have not seen anything like the AddrPort error you got after. I can try to debug it if you can provide an example configuration to reproduce it, otherwise I think this PR should be closed in favor of yours.