Numerical Domains Unsupported #170

New Issue

2025-11-13T11:52:03-06:00

GiteaMirror commented

2025-11-13 11:52:03 -06:00

Originally created by @ultimaterex on GitHub (Mar 22, 2025).

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)

Originally created by @ultimaterex on GitHub (Mar 22, 2025). Wanted to setup pangolin on a cheap [1.111b domain](https://gen.xyz/1111b) 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)

GiteaMirror closed this issue

2025-11-13 11:52:03 -06:00

GiteaMirror commented

2025-11-13 11:52:04 -06:00

@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, .111b is 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 like abc123.com would work I think.

Are there any errors from the server when using the numerical domain?

@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`, `.111b` is 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 like `abc123.com` would work I think. Are there any errors from the server when using the numerical domain?

GiteaMirror commented

2025-11-13 11:52:04 -06:00

@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 found

Traefik does seem to be running into an error:

2025-03-22T22:17:44Z INF Traefik version 3.3.3 built on 2025-01-31T14:55:01Z version=3.3.3
2025-03-22T22:17:44Z INF 
Stats collection is disabled.
Help us improve Traefik by turning this feature on :)
More details on: https://doc.traefik.io/traefik/contributing/data-collection/
2025-03-22T22:17:44Z INF Loading plugins... plugins=["badger"]
2025-03-22T22:17:45Z INF Plugins loaded. plugins=["badger"]
2025-03-22T22:17:45Z INF Starting provider aggregator *aggregator.ProviderAggregator
2025-03-22T22:17:45Z INF Starting provider *file.Provider
2025-03-22T22:17:45Z INF Starting provider *traefik.Provider
2025-03-22T22:17:45Z INF Starting provider *http.Provider
2025-03-22T22:17:45Z INF Starting provider *acme.ChallengeTLSALPN
2025-03-22T22:17:45Z INF Starting provider *acme.Provider
2025-03-22T22:17:45Z INF Testing certificate renew... acmeCA=https://acme-v02.api.letsencrypt.org/directory providerName=letsencrypt.acme
2025-03-22T22:17:48Z INF Register... providerName=letsencrypt.acme
2025-03-22T22:27:45Z WRN A new release of Traefik has been found: 3.3.4. Please consider updating.
2025-03-22T22:29:30Z ERR Cannot retrieve the ACME challenge for 0123456789.xyz (token "letsencrypt_b683acb82cef77c558e7fc67331f521a") providerName=acme
2025-03-22T22:29:31Z ERR Cannot retrieve the ACME challenge for mail.0123456789.xyz (token "letsencrypt_3985429026fc545234dda80f8a1557a2") providerName=acme
2025-03-22T22:29:31Z ERR Cannot retrieve the ACME challenge for mailadmin.0123456789.xyz (token "letsencrypt_d0b9fcfcd45fae64511139bb2584be6d") providerName=acme
2025-03-22T22:29:31Z ERR Cannot retrieve the ACME challenge for webmail.0123456789.xyz (token "letsencrypt_807ff025aab9fe307795d19656780d23") providerName=acme

pangolin

> @fosrl/pangolin@0.0.0 start
> NODE_OPTIONS=--enable-source-maps NODE_ENV=development ENVIRONMENT=prod sh -c 'node dist/migrations.mjs && node dist/server.mjs'
Running migrations...
Migrations completed successfully.
2025-03-22T22:17:39.362Z [info]: Server admin (pangolin@selby.one) created
2025-03-22T22:17:41.013Z [info]: API server is running on http://localhost:3000
2025-03-22T22:17:41.014Z [info]: Internal server is running on http://localhost:3001
2025-03-22T22:17:41.914Z [info]: Next.js server is running on http://localhost:3002
2025-03-22T22:17:43.663Z [info]: Created new exit node Exit Node 3VS3Sg/+ with address 100.89.128.1/24 and port 51820

gerbil

INFO: 2025/03/22 22:17:43 Fetching remote config from http://pangolin:3001/api/v1/gerbil/get-config
INFO: 2025/03/22 22:17:43 Created WireGuard interface wg0
INFO: 2025/03/22 22:17:43 Assigned IP address 100.89.128.1/24 to interface wg0
INFO: 2025/03/22 22:17:43 Attempting to delete existing MSS clamping rule for chain INPUT
INFO: 2025/03/22 22:17:43 Attempting to delete existing MSS clamping rule for chain OUTPUT
INFO: 2025/03/22 22:17:43 Attempting to delete existing MSS clamping rule for chain FORWARD
INFO: 2025/03/22 22:17:43 Adding MSS clamping rule for chain INPUT
INFO: 2025/03/22 22:17:43 Successfully added and verified MSS clamping rule for chain INPUT
INFO: 2025/03/22 22:17:43 Adding MSS clamping rule for chain OUTPUT
INFO: 2025/03/22 22:17:43 Successfully added and verified MSS clamping rule for chain OUTPUT
INFO: 2025/03/22 22:17:43 Adding MSS clamping rule for chain FORWARD
INFO: 2025/03/22 22:17:43 Successfully added and verified MSS clamping rule for chain FORWARD
INFO: 2025/03/22 22:17:43 WireGuard interface wg0 created and configured
INFO: 2025/03/22 22:17:43 Starting server on :3003

@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 found` Traefik does seem to be running into an error: ``` 2025-03-22T22:17:44Z INF Traefik version 3.3.3 built on 2025-01-31T14:55:01Z version=3.3.3 2025-03-22T22:17:44Z INF Stats collection is disabled. Help us improve Traefik by turning this feature on :) More details on: https://doc.traefik.io/traefik/contributing/data-collection/ 2025-03-22T22:17:44Z INF Loading plugins... plugins=["badger"] 2025-03-22T22:17:45Z INF Plugins loaded. plugins=["badger"] 2025-03-22T22:17:45Z INF Starting provider aggregator *aggregator.ProviderAggregator 2025-03-22T22:17:45Z INF Starting provider *file.Provider 2025-03-22T22:17:45Z INF Starting provider *traefik.Provider 2025-03-22T22:17:45Z INF Starting provider *http.Provider 2025-03-22T22:17:45Z INF Starting provider *acme.ChallengeTLSALPN 2025-03-22T22:17:45Z INF Starting provider *acme.Provider 2025-03-22T22:17:45Z INF Testing certificate renew... acmeCA=https://acme-v02.api.letsencrypt.org/directory providerName=letsencrypt.acme 2025-03-22T22:17:48Z INF Register... providerName=letsencrypt.acme 2025-03-22T22:27:45Z WRN A new release of Traefik has been found: 3.3.4. Please consider updating. 2025-03-22T22:29:30Z ERR Cannot retrieve the ACME challenge for 0123456789.xyz (token "letsencrypt_b683acb82cef77c558e7fc67331f521a") providerName=acme 2025-03-22T22:29:31Z ERR Cannot retrieve the ACME challenge for mail.0123456789.xyz (token "letsencrypt_3985429026fc545234dda80f8a1557a2") providerName=acme 2025-03-22T22:29:31Z ERR Cannot retrieve the ACME challenge for mailadmin.0123456789.xyz (token "letsencrypt_d0b9fcfcd45fae64511139bb2584be6d") providerName=acme 2025-03-22T22:29:31Z ERR Cannot retrieve the ACME challenge for webmail.0123456789.xyz (token "letsencrypt_807ff025aab9fe307795d19656780d23") providerName=acme ``` **pangolin** ``` > @fosrl/pangolin@0.0.0 start > NODE_OPTIONS=--enable-source-maps NODE_ENV=development ENVIRONMENT=prod sh -c 'node dist/migrations.mjs && node dist/server.mjs' Running migrations... Migrations completed successfully. 2025-03-22T22:17:39.362Z [info]: Server admin (pangolin@selby.one) created 2025-03-22T22:17:41.013Z [info]: API server is running on http://localhost:3000 2025-03-22T22:17:41.014Z [info]: Internal server is running on http://localhost:3001 2025-03-22T22:17:41.914Z [info]: Next.js server is running on http://localhost:3002 2025-03-22T22:17:43.663Z [info]: Created new exit node Exit Node 3VS3Sg/+ with address 100.89.128.1/24 and port 51820 ``` **gerbil** ``` INFO: 2025/03/22 22:17:43 Fetching remote config from http://pangolin:3001/api/v1/gerbil/get-config INFO: 2025/03/22 22:17:43 Created WireGuard interface wg0 INFO: 2025/03/22 22:17:43 Assigned IP address 100.89.128.1/24 to interface wg0 INFO: 2025/03/22 22:17:43 Attempting to delete existing MSS clamping rule for chain INPUT INFO: 2025/03/22 22:17:43 Attempting to delete existing MSS clamping rule for chain OUTPUT INFO: 2025/03/22 22:17:43 Attempting to delete existing MSS clamping rule for chain FORWARD INFO: 2025/03/22 22:17:43 Adding MSS clamping rule for chain INPUT INFO: 2025/03/22 22:17:43 Successfully added and verified MSS clamping rule for chain INPUT INFO: 2025/03/22 22:17:43 Adding MSS clamping rule for chain OUTPUT INFO: 2025/03/22 22:17:43 Successfully added and verified MSS clamping rule for chain OUTPUT INFO: 2025/03/22 22:17:43 Adding MSS clamping rule for chain FORWARD INFO: 2025/03/22 22:17:43 Successfully added and verified MSS clamping rule for chain FORWARD INFO: 2025/03/22 22:17:43 WireGuard interface wg0 created and configured INFO: 2025/03/22 22:17:43 Starting server on :3003 ```

GiteaMirror commented

2025-11-13 11:52:04 -06:00

@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

@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

GiteaMirror commented

2025-11-13 11:52:04 -06:00

@miloschwartz commented on GitHub (Mar 23, 2025):

Ah duh, thanks 1.111b makes 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.

@miloschwartz commented on GitHub (Mar 23, 2025): Ah duh, thanks `1.111b` makes 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.

GiteaMirror commented

2025-11-13 11:52:04 -06:00

@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!

@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!