mirror of
https://github.com/fosrl/pangolin.git
synced 2026-05-21 09:21:15 -05:00
[GH-ISSUE #208] Error Message "no available Server" #12148
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @StephanStrunk on GitHub (Feb 15, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/208
Im running Pangolin on a Ionos-XS-Server (Ubuntu 24.04) and Newt on my Local Synology NAS (docker compose). It seems all is operating perfect. The domain of pangolin on my Ionos-Server works and also the domain of pangolin defined in the pangolin-installation.
Wenn I'm using a domain of a ressource in pangolin I always get the massage "no available server".
What got wrong ? Any ideas ?
@oschwartz10612 commented on GitHub (Feb 15, 2025):
HI!
I think we will need a little more information.
Do you have your newt connected? Can you send the Newt logs?
Have you created your targets on your resource and do they point correctly to the internal addresses on your network running newt?
What are you trying to proxy?
@StephanStrunk commented on GitHub (Feb 15, 2025):
Hi,
sorry - this was lettle to less info - here more details:
System/installation
What I want ist to make my home-Network able to access from outside as I have a DSLite (dualstack) connection from my Privider (Deutsche Glasfaser) and no ipv4-adress.
@StephanStrunk commented on GitHub (Feb 15, 2025):
Oh wait! with your question abou the target I ched this again and found that the target-definition in pangolin was not saved. I did that and now got
a) from my router (fritzbox) an error by security reasons:
Der DNS-Rebind-Schutz Ihrer FRITZ!Box hat Ihre Anfrage aus Sicherheitsgründen abgewiesen.
Der Host-Header Ihrer Anfrage stimmt nicht mit dem Namen der FRITZ!Box überein.
Wenn Sie über einen anderen Hostnamen auf die FRITZ!Box zugreifen wollen, ergänzen Sie diesen bitte als Ausnahme in der Benutzeroberfläche Ihrer FRITZ!Box unter "Heimnetz > Netzwerk > Netzwerkeinstellungen" im Bereich "DNS-Rebind-Schutz"
b) from the docker-apps: "bad gateway"
thanks for one step further - still having someting to solve....
Stephan
@oschwartz10612 commented on GitHub (Feb 15, 2025):
The null:null issue in the newt you are seeing might be an issue. Are you on the latest version of newt and Pangolin? Pangolin should be version
beta.14right now.Bad gateway usually means it is having trouble addressing the docker app from newt. Is the docker container on a different computer on your network or also on Synology?
Translating the German it looks like it is saying
The host header of your request does not match the name of the FRITZ!Box. This is because the host from the external service hitting Traefik in Pangolin is something.yourdomain.com and is not the same as it is addressed internally. Is there a way to turn this off inside of your appliance?@StephanStrunk commented on GitHub (Feb 16, 2025):
Hi,
Unfortunately I can’t find the Version of pangolin - where do I find that (Server oder Website ?)
The issue of FRITZ!Box seems to be solved with an exception for the domain (see attached photo)
In general the problem seems to be the CGN of Deutsche Glkasfaser: the external IP ist different from the local internal IPv4 (external always the same and seems to be one of the provider). Once I use that external ipv4 with a defined Port this works. The internal IP does not
And yes: the docker-app runs on the same NAS as newt
@StephanStrunk commented on GitHub (Feb 16, 2025):
Is there any way to work with the internal IPv4 ?
Thanks so much
Stephan
@oschwartz10612 commented on GitHub (Feb 16, 2025):
The version should be at the very bottom of the page in Pangolin or in your docker-compose.yml file.
Unfortunately I dont know much about this appliance so I can not tell you how to configure it to work with the system. I think as you have figured out it cares about the host header and by extension the IP you use to address it. Newt is just a TCP proxy and Traefik has to address Newt to redirect to your resource.
My guess is when addressing from public it does not care about the host header for some reason, I would look for some security settings on the lan to do the same thing.
@StephanStrunk commented on GitHub (Feb 16, 2025):
Hi,
thanks - the version at the bottom of pangolin shows v.1.0.0. beta12. Do I need to update on my Cloud-Server ? (and how to do that ?)
As I am able to adress the fritzbox by its regular ipv4 with that mentioned exception I will look for the same on my Synology-NAS. good idea
Thanks so far for you very helpful support!!
@oschwartz10612 commented on GitHub (Feb 16, 2025):
You can follow this guide: https://docs.fossorial.io/Getting%20Started/how-to-update
Sounds good glad I can help. I will close this for now but feel free to reopen.