Trying to setup pangolin for the first time.
Used the install script, but Traefik wouldn't let me get certificates through https challenge.
Dashboard wasn't available and I got this:
I can see "WireGuard interface wg0 created and configured", should interface "wg0" be visible on my server? If so, it isnt:
(pangolin traefik and gerbil running here:)
Dashboard (pangolin.DOMAIN.com) still wasn't available.
I checked my 80, 443, 21820, 51820 ports:
These ports are also port forwarded in my router settings. (some random ubee router GUI but I think this is ok)
Without port forwarding it gave me the same result.
I'm trying to keep everything as simple and to "stock" as possible to even see it working at all.
But no luck in two days.
I was using a Cloudflare tunnel before which basically worked out of the box.
This is how my DNS records look:
I can't figure out why the basic (https challenge) didn't work, as the server is basically empty (not clean install but not much going on either). I also can't figure out why it doesn't work with a working(?) dns challenge.
Any help would be appreciated
Environment
OS Type & Version: home server on Ubuntu 22.04.3 LTS
Pangolin Version: 1.15.0
Gerbil Version: 1.3.0
Traefik Version: 3.6.7
Newt Version: -
To Reproduce
-install with script as usual idk
Expected Behavior
-dashboard available
Originally created by @hinczyker on GitHub (Jan 24, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2322
### Describe the Bug
Trying to setup pangolin for the first time.
Used the install script, but Traefik wouldn't let me get certificates through https challenge.
Dashboard wasn't available and I got this:
<img width="1356" height="102" alt="Image" src="https://github.com/user-attachments/assets/72588206-43cc-45d4-a579-cbcbf79a1cfd" />
I changed Traefik to DNS challenge wildcard domains (https://docs.pangolin.net/self-host/advanced/wild-card-domains) and I don't get any errors in docker compose logs from that anymore. Here's how it looks:
<img width="1062" height="785" alt="Image" src="https://github.com/user-attachments/assets/e6d058fd-36ac-473c-a2a0-91e549dc3710" />
I can see "WireGuard interface wg0 created and configured", should interface "wg0" be visible on my server? If so, it isnt:
(pangolin traefik and gerbil running here:)
<img width="388" height="214" alt="Image" src="https://github.com/user-attachments/assets/9a800894-c6fe-43af-8d19-d6911bd8f566" />
Dashboard (pangolin.DOMAIN.com) still wasn't available.
<img width="836" height="260" alt="Image" src="https://github.com/user-attachments/assets/5830519f-82f8-4fd6-9e7d-4477a85d9738" />
I checked my 80, 443, 21820, 51820 ports:
<img width="420" height="259" alt="Image" src="https://github.com/user-attachments/assets/51e068b4-8f5f-4611-bbe2-54d5c865a340" />
These ports are also port forwarded in my router settings. (some random ubee router GUI but I think this is ok)
Without port forwarding it gave me the same result.
<img width="443" height="158" alt="Image" src="https://github.com/user-attachments/assets/ba13de96-2cb7-4409-8a62-d2dd2993061c" />
I'm trying to keep everything as simple and to "stock" as possible to even see it working at all.
But no luck in two days.
I was using a Cloudflare tunnel before which basically worked out of the box.
This is how my DNS records look:
<img width="1562" height="153" alt="Image" src="https://github.com/user-attachments/assets/c7c09033-79c9-4999-ad89-c858549b93ee" />
I can't figure out why the basic (https challenge) didn't work, as the server is basically empty (not clean install but not much going on either). I also can't figure out why it doesn't work with a working(?) dns challenge.
Any help would be appreciated
### Environment
- OS Type & Version: home server on Ubuntu 22.04.3 LTS
- Pangolin Version: 1.15.0
- Gerbil Version: 1.3.0
- Traefik Version: 3.6.7
- Newt Version: -
### To Reproduce
-install with script as usual idk
### Expected Behavior
-dashboard available
netstat -tunlp
# run "apt install net-tools" if not installed
could you also share your docker-compose.yml file ?
what is the output of cd /the/pangolin/compose/path && docker compose ps ?
<!-- gh-comment-id:3795603959 -->
@barnabehvrd commented on GitHub (Jan 24, 2026):
Hello !
Could you try to run :
```
netstat -tunlp
# run "apt install net-tools" if not installed
```
could you also share your `docker-compose.yml` file ?
what is the output of `cd /the/pangolin/compose/path && docker compose ps` ?
Well, having SSL issues shouldn't give you a timed out error.
Can you login to pangolin using the local ip of your server (if this is a physical server on the same network as yours) ? On both 80 and 443 ports ?
<!-- gh-comment-id:3795667295 -->
@barnabehvrd commented on GitHub (Jan 24, 2026):
Well, having SSL issues shouldn't give you a timed out error.
Can you login to pangolin using the local ip of your server (if this is a physical server on the same network as yours) ? On both 80 and 443 ports ?
Also, i guess docker compose logs -n 10 doesn't give any usefull information ?
<!-- gh-comment-id:3795668612 -->
@barnabehvrd commented on GitHub (Jan 24, 2026):
Also, i guess `docker compose logs -n 10` doesn't give any usefull information ?
Logs are visible in the second picture, nothing changed since then from what I can see.
I actually can do http://192.168.0.230:443/ and http://192.168.0.230:80/ and it does resolve, but to a 404:
Yeah the server is right next to me, it's a laptop im ssh'd into.
<!-- gh-comment-id:3795671332 -->
@hinczyker commented on GitHub (Jan 24, 2026):
Logs are visible in the second picture, nothing changed since then from what I can see.
I actually can do http://192.168.0.230:443/ and http://192.168.0.230:80/ and it does resolve, but to a 404:
Yeah the server is right next to me, it's a laptop im ssh'd into.
<img width="570" height="104" alt="Image" src="https://github.com/user-attachments/assets/b9b4a313-0836-4939-8649-30b42bf0fc9e" />
Trying http://PUBLICIP:443 or 80 times out though.
Alright I went nuclear and reinstalled the OS on my server. It's a fully clean install now.
Directly after using the Pangolin install script it still gives me the same error about http challenge certs:
And dashboard still times out.
<!-- gh-comment-id:3795793889 -->
@hinczyker commented on GitHub (Jan 25, 2026):
Alright I went nuclear and reinstalled the OS on my server. It's a fully clean install now.
Directly after using the Pangolin install script it still gives me the same error about http challenge certs:
<img width="1112" height="17" alt="Image" src="https://github.com/user-attachments/assets/f556ca49-b301-4dc4-b18a-b2418adb2ab4" />
And dashboard still times out.
If you can connect to the server at 192.168.xxx.xxx, it means that the server is listening on 0.0.0.0. The issue is probably misconfigured NAT.
My guess is that your router isn't redirecting ports 80 and 443 to your server. Despite having the correct DNS records, the router isn't responding to the 80/443 ports.
Unfortunately, I can't help you with Ubee routers.
Are you sure you have a full stack IP ?
<!-- gh-comment-id:3796470823 -->
@barnabehvrd commented on GitHub (Jan 25, 2026):
If you can connect to the server at 192.168.xxx.xxx, it means that the server is listening on 0.0.0.0. The issue is probably misconfigured NAT.
My guess is that your router isn't redirecting ports 80 and 443 to your server. Despite having the correct DNS records, the router isn't responding to the 80/443 ports.
Unfortunately, I can't help you with Ubee routers.
Are you sure you have a full stack IP ?
I think this is the right track, I checked the manual for this router and fixed the port forwarding setup,("External IP" needs to be set to 192.168.0.0 apparently) but looking at any service that checks for open ports everything shows that these ports are all closed. I'll be able to test this on a different isp with a different router that I know has working port forwarding.
<!-- gh-comment-id:3796687408 -->
@hinczyker commented on GitHub (Jan 25, 2026):
I think this is the right track, I checked the manual for this router and fixed the port forwarding setup,("External IP" needs to be set to 192.168.0.0 apparently) but looking at any service that checks for open ports everything shows that these ports are all closed. I'll be able to test this on a different isp with a different router that I know has working port forwarding.
Yeah the previous ISP didn't give me a public ipv4 address. It had cgnat I'm pretty sure.
Well, it works now, thanks for help!
<!-- gh-comment-id:3798496413 -->
@hinczyker commented on GitHub (Jan 26, 2026):
Yeah the previous ISP didn't give me a public ipv4 address. It had cgnat I'm pretty sure.
Well, it works now, thanks for help!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @hinczyker on GitHub (Jan 24, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2322
Describe the Bug
Trying to setup pangolin for the first time.
Used the install script, but Traefik wouldn't let me get certificates through https challenge.
Dashboard wasn't available and I got this:
I changed Traefik to DNS challenge wildcard domains (https://docs.pangolin.net/self-host/advanced/wild-card-domains) and I don't get any errors in docker compose logs from that anymore. Here's how it looks:
Dashboard (pangolin.DOMAIN.com) still wasn't available.
I checked my 80, 443, 21820, 51820 ports:
These ports are also port forwarded in my router settings. (some random ubee router GUI but I think this is ok)
Without port forwarding it gave me the same result.
I'm trying to keep everything as simple and to "stock" as possible to even see it working at all.
But no luck in two days.
I was using a Cloudflare tunnel before which basically worked out of the box.
This is how my DNS records look:
I can't figure out why the basic (https challenge) didn't work, as the server is basically empty (not clean install but not much going on either). I also can't figure out why it doesn't work with a working(?) dns challenge.
Any help would be appreciated
Environment
To Reproduce
-install with script as usual idk
Expected Behavior
-dashboard available
@barnabehvrd commented on GitHub (Jan 24, 2026):
Hello !
Could you try to run :
could you also share your
docker-compose.ymlfile ?what is the output of
cd /the/pangolin/compose/path && docker compose ps?@hinczyker commented on GitHub (Jan 24, 2026):
Heres netstat and docker ps,
docker-compose.yml is mostly unchanged(from basic installer) just with added secrets for my CF api token:
Here's also what I changed in traefik configs:
Dynamic:
other traefik config:
@barnabehvrd commented on GitHub (Jan 24, 2026):
Well, having SSL issues shouldn't give you a timed out error.
Can you login to pangolin using the local ip of your server (if this is a physical server on the same network as yours) ? On both 80 and 443 ports ?
@barnabehvrd commented on GitHub (Jan 24, 2026):
Also, i guess
docker compose logs -n 10doesn't give any usefull information ?@hinczyker commented on GitHub (Jan 24, 2026):
Logs are visible in the second picture, nothing changed since then from what I can see.
I actually can do http://192.168.0.230:443/ and http://192.168.0.230:80/ and it does resolve, but to a 404:
Yeah the server is right next to me, it's a laptop im ssh'd into.
Trying http://PUBLICIP:443 or 80 times out though.
@hinczyker commented on GitHub (Jan 25, 2026):
Alright I went nuclear and reinstalled the OS on my server. It's a fully clean install now.
Directly after using the Pangolin install script it still gives me the same error about http challenge certs:
And dashboard still times out.
@barnabehvrd commented on GitHub (Jan 25, 2026):
If you can connect to the server at 192.168.xxx.xxx, it means that the server is listening on 0.0.0.0. The issue is probably misconfigured NAT.
My guess is that your router isn't redirecting ports 80 and 443 to your server. Despite having the correct DNS records, the router isn't responding to the 80/443 ports.
Unfortunately, I can't help you with Ubee routers.
Are you sure you have a full stack IP ?
@hinczyker commented on GitHub (Jan 25, 2026):
I think this is the right track, I checked the manual for this router and fixed the port forwarding setup,("External IP" needs to be set to 192.168.0.0 apparently) but looking at any service that checks for open ports everything shows that these ports are all closed. I'll be able to test this on a different isp with a different router that I know has working port forwarding.
@hinczyker commented on GitHub (Jan 26, 2026):
Yeah the previous ISP didn't give me a public ipv4 address. It had cgnat I'm pretty sure.
Well, it works now, thanks for help!