Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - The_Istar

#1
Patch seems to have worked.
It did require a reboot of the system though, a simple stop and start of Caddy was not enough.

Thanks for the quick support!
#2
That was fast. Thanks. Looking forward to seeing this implemented.
#3
Since the last update to 24.7.10 it seems my redirects no longer work.

It seems it does pick up the request properly but then redirects to a URL that looks something like this:

http://bazarr/10.67.0.52:6767/10.67.0.52:6767/10.67.0.52:6767/10.67.0.52:6767/10.67.0.52:6767/10.67.0.52:6767/10.67.0.52:6767/10.67.0.52:6767/10.67.0.52:6767/10.67.0.52:6767/10.67.0.52:6767/10.67.0.52:6767/10.67.0.52:6767/10.67.0.52:6767/10.67.0.52:6767/10.67.0.52:6767/10.67.0.52:6767/10.67.0.52:6767/10.67.0.52:6767/10.67.0.52:6767/.......
This address goes on like this until finally the request is aborted with: ERR_RESPONSE_HEADERS_TOO_BIG

My Caddy file is attached.

Looking at it I do not see any reason why the redirects should behave the way they do. There does not seem to be anything different in the Caddy file itself than before the update, as far as I can see.
#4
Thanks for the reply. I also tried a lot of different configuration yet I can't get ti to work.
The annoying thing is that it works fine when using OpenVPN. But not with Wireguard.
#5
You ever got this working?

In the old days you could get this working giving the interface a static IP, but this stopped working a while back.
Since then I have had no luck getting this to work again.
#6
Anybody else have an idea?
#7
Would you be willing to share what you did with us?
So people less good at scripting might use your solution as well? :)