mirror of
https://github.com/fosrl/pangolin.git
synced 2026-05-05 15:34:42 -05:00
[GH-ISSUE #381] Numerical Domains Unsupported #1423
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 @ultimaterex on GitHub (Mar 22, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/381
Wanted to setup pangolin on a cheap 1.111b domain and used the automated install. Post install the site wasn't reachable at my set pangolin address, tried this on a normal alphabetical domain and the install worked flawlessly.
I used the exact same install params in the numerical domain vs the alphabetical domain and couldn't get the numerical to work. (Crowdsec + smtp)
@miloschwartz commented on GitHub (Mar 22, 2025):
Mmm that's odd. I can't think of an obvious reason why you wouldn't be able to have numbers in the domain. Although in the example you gave,
1.111b,.111bis not a valid TLD that I am aware of. That could be the reason why if this is actually the domain you were using. Otherwise something likeabc123.comwould work I think.Are there any errors from the server when using the numerical domain?
@ultimaterex commented on GitHub (Mar 22, 2025):
Ah a 1.111b domain is just 6-9 number .xyz that they sell for .99c/year eg: "0123456789.xyz"
@miloschwartz
I setup a new instance of pangolin on another host without crowdsec to reduce complexity
when navigating to pangolin.domain.xyz
I only get
404 page not foundTraefik does seem to be running into an error:
pangolin
gerbil
@hhftechnology commented on GitHub (Mar 23, 2025):
my 2 cents are port 80 is not open i suppose or there is some issue with port 80
@miloschwartz commented on GitHub (Mar 23, 2025):
Ah duh, thanks
1.111bmakes more sense now!As @hhftechnology said, I would check the ports on the VPS to make sure they're open. Also triple check your domain DNS records are pointing to the IP of the VPS, and that they actually resolve to the IP.
@ultimaterex commented on GitHub (Mar 24, 2025):
Weirdly enough, it started working after a few hours, seems the issue was DNS/Cloudflare related, --my bad guys, thanks for the help!