Why it does not start? #204

Closed
opened 2025-11-13 11:52:53 -06:00 by GiteaMirror · 9 comments
Owner

Originally created by @pippo73 on GitHub (Mar 31, 2025).

Hi all
I'm trying to start your app, but I cannot understand what is going wrong.
Here you can find the docker and the config files
pango.zip
On cloudflare I've set the A record pointing to my IP, and just to be sure I've added also a A record for https://pangolin.thisismysite.com
when I start everything the docker logs for the 3 apps and everything is ok, but if I try to connect to https://pangolin.thisismysite.com, to https://thisismysite.com, or even to my internal ip address nothing happens.

How can I test where is the problem? Sorry but I have no more infos

Originally created by @pippo73 on GitHub (Mar 31, 2025). Hi all I'm trying to start your app, but I cannot understand what is going wrong. Here you can find the docker and the config files [pango.zip](https://github.com/user-attachments/files/19540949/pango.zip) On cloudflare I've set the A record pointing to my IP, and just to be sure I've added also a A record for _https://pangolin.thisismysite.com_ when I start everything the docker logs for the 3 apps and everything is ok, but if I try to connect to https://pangolin.thisismysite.com, to https://thisismysite.com, or even to my internal ip address nothing happens. How can I test where is the problem? Sorry but I have no more infos
Author
Owner

@oschwartz10612 commented on GitHub (Apr 1, 2025):

Hello!

What do you mean nothing happens? Do you get any errors in the browser? If so could you post them?

Could you please also post your docker logs and remove anything you do not want shared? You can run docker compose logs

@oschwartz10612 commented on GitHub (Apr 1, 2025): Hello! What do you mean nothing happens? Do you get any errors in the browser? If so could you post them? Could you please also post your docker logs and remove anything you do not want shared? You can run `docker compose logs`
Author
Owner

@Node815 commented on GitHub (Apr 1, 2025):

I'm facing the same issue, I pointed the A record to my domain in Cloudflare (I would love to get way from them) :) It's connected to an Amazon Lightsail VPS server. Here are the logs from the container:

root@ip-172-26-14-92:/home/admin# docker start pangolin
pangolin
root@ip-172-26-14-92:/home/admin# docker logs -f 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-04-01T01:30:03.705Z [info]: Server admin (myemail@example.com) created
2025-04-01T01:30:06.339Z [info]: API server is running on http://localhost:3000
2025-04-01T01:30:06.340Z [info]: Internal server is running on http://localhost:3001
2025-04-01T01:30:08.025Z [info]: Next.js server is running on http://localhost:3002
npm error path /app
npm error command failed
npm error signal SIGTERM
npm error command sh -c NODE_OPTIONS=--enable-source-maps NODE_ENV=development ENVIRONMENT=prod sh -c 'node dist/migrations.mjs && node dist/server.mjs'
npm notice
npm notice New major version of npm available! 10.8.2 -> 11.2.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.2.0
npm notice To update run: npm install -g npm@11.2.0
npm notice
npm error A complete log of this run can be found in: /root/.npm/_logs/2025-04-01T01_29_49_347Z-debug-0.log

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

Starting migrations from version 1.1.0
Migrations to run:
All migrations completed successfully
2025-04-01T02:01:14.212Z [info]: Server admin (myemail@example.com) already exists
2025-04-01T02:01:15.126Z [info]: API server is running on http://localhost:3000
2025-04-01T02:01:15.127Z [info]: Internal server is running on http://localhost:3001
2025-04-01T02:01:16.130Z [info]: Next.js server is running on http://localhost:3002

When I attempt to go to my domain, I get a message that the server is down.

Image

NOTE: I did select the "Free" instance with the 90 day trial so it's a very minimal provisioning on their side. It's a 512mb memory alllocation:

root@ip-172-26-14-92:/home/admin/config# free -m
total used free shared buff/cache available
Mem: 447 293 16 0 150 154
Swap: 0 0 0

I believe your docs say 1gb is recommended, so I'm not sure if this would have been the cause for this or not.

@Node815 commented on GitHub (Apr 1, 2025): I'm facing the same issue, I pointed the A record to my domain in Cloudflare (I would love to get way from them) :) It's connected to an Amazon Lightsail VPS server. Here are the logs from the container: > root@ip-172-26-14-92:/home/admin# docker start pangolin >pangolin >root@ip-172-26-14-92:/home/admin# docker logs -f 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-04-01T01:30:03.705Z [info]: Server admin (myemail@example.com) created >2025-04-01T01:30:06.339Z [info]: API server is running on http://localhost:3000 > 2025-04-01T01:30:06.340Z [info]: Internal server is running on http://localhost:3001 > 2025-04-01T01:30:08.025Z [info]: Next.js server is running on http://localhost:3002 > npm error path /app > npm error command failed > npm error signal SIGTERM > npm error command sh -c NODE_OPTIONS=--enable-source-maps NODE_ENV=development ENVIRONMENT=prod sh -c 'node dist/migrations.mjs && node dist/server.mjs' > npm notice > npm notice New major version of npm available! 10.8.2 -> 11.2.0 > npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.2.0 > npm notice To update run: npm install -g npm@11.2.0 > npm notice > npm error A complete log of this run can be found in: /root/.npm/_logs/2025-04-01T01_29_49_347Z-debug-0.log > @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' > > Starting migrations from version 1.1.0 > Migrations to run: > All migrations completed successfully > 2025-04-01T02:01:14.212Z [info]: Server admin (myemail@example.com) already exists > 2025-04-01T02:01:15.126Z [info]: API server is running on http://localhost:3000 > 2025-04-01T02:01:15.127Z [info]: Internal server is running on http://localhost:3001 > 2025-04-01T02:01:16.130Z [info]: Next.js server is running on http://localhost:3002 When I attempt to go to my domain, I get a message that the server is down. ![Image](https://github.com/user-attachments/assets/80fcf4cb-0022-4fee-bf71-2811be7cea97) **NOTE:** I did select the "Free" instance with the 90 day trial so it's a very minimal provisioning on their side. It's a 512mb memory alllocation: root@ip-172-26-14-92:/home/admin/config# free -m total used free shared buff/cache available Mem: 447 293 16 0 150 154 Swap: 0 0 0 I believe your docs say 1gb is recommended, so I'm not sure if this would have been the cause for this or not.
Author
Owner

@pippo73 commented on GitHub (Apr 1, 2025):

Hello!

What do you mean nothing happens? Do you get any errors in the browser? If so could you post them?

Could you please also post your docker logs and remove anything you do not want shared? You can run docker compose logs

I'm sorry yesterday it was really late for me and I was really disappointed 😥
Now I'm more fresh and I can be more "usefull"

# docker compose stop && docker system prune && docker compose up -d --remove-orphans --force-recreate
[+] Stopping 3/3
 ✔ Container traefik   Stopped                                                                                                                           0.1s
 ✔ Container gerbil    Stopped                                                                                                                           0.3s
 ✔ Container pangolin  Stopped                                                                                                                           5.2s
WARNING! This will remove:
  - all stopped containers
  - all networks not used by at least one container
  - all dangling images
  - unused build cache

Are you sure you want to continue? [y/N] y
Deleted Containers:
c7abeee8dc988e5452861c92bf9a2a81d1a47aa2d311679d5240e0a04fa45885
ffc0ac53df404afcbf93c7696205261c3ee62e17376884ac072cf3e40ce73dd9
d692c032b304b53d38384930656cc661d2c7328d480ece84027b93c4539591cd

Deleted Networks:
pangolin

Total reclaimed space: 17.16kB
[+] Running 4/4
 ✔ Network pangolin    Created                                                                                                                           0.0s
 ✔ Container pangolin  Healthy                                                                                                                          22.9s
 ✔ Container gerbil    Started                                                                                                                          14.1s
 ✔ Container traefik   Started     

Hera are the logs


root@Pangolin:~# docker logs traefik
2025-04-01T07:50:07Z INF Traefik version 3.3.3 built on 2025-01-31T14:55:01Z version=3.3.3
2025-04-01T07:50:07Z 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-04-01T07:50:07Z INF Loading plugins... plugins=["badger"]
2025-04-01T07:50:08Z INF Plugins loaded. plugins=["badger"]
2025-04-01T07:50:08Z INF Starting provider aggregator *aggregator.ProviderAggregator
2025-04-01T07:50:08Z INF Starting provider *file.Provider
2025-04-01T07:50:08Z INF Starting provider *traefik.Provider
2025-04-01T07:50:08Z INF Starting provider *http.Provider
2025-04-01T07:50:08Z INF Starting provider *acme.ChallengeTLSALPN
2025-04-01T07:50:08Z INF Starting provider *acme.Provider
2025-04-01T07:50:08Z INF Testing certificate renew... acmeCA=https://acme-v02.api.letsencrypt.org/directory providerName=letsencrypt.acme
root@Pangolin:~#
root@Pangolin:~#
root@Pangolin:~# docker logs gerbil
INFO: 2025/04/01 07:50:07 Fetching remote config from http://pangolin:3001/api/v1/gerbil/get-config
INFO: 2025/04/01 07:50:07 Created WireGuard interface wg0
INFO: 2025/04/01 07:50:07 Assigned IP address 100.89.128.1/24 to interface wg0
INFO: 2025/04/01 07:50:07 Attempting to delete existing MSS clamping rule for chain INPUT
INFO: 2025/04/01 07:50:07 Attempting to delete existing MSS clamping rule for chain OUTPUT
INFO: 2025/04/01 07:50:07 Attempting to delete existing MSS clamping rule for chain FORWARD
INFO: 2025/04/01 07:50:07 Adding MSS clamping rule for chain INPUT
INFO: 2025/04/01 07:50:07 Successfully added and verified MSS clamping rule for chain INPUT
INFO: 2025/04/01 07:50:07 Adding MSS clamping rule for chain OUTPUT
INFO: 2025/04/01 07:50:07 Successfully added and verified MSS clamping rule for chain OUTPUT
INFO: 2025/04/01 07:50:07 Adding MSS clamping rule for chain FORWARD
INFO: 2025/04/01 07:50:07 Successfully added and verified MSS clamping rule for chain FORWARD
INFO: 2025/04/01 07:50:07 WireGuard interface wg0 created and configured
INFO: 2025/04/01 07:50:07 Starting server on :3003
root@Pangolin:~#
root@Pangolin:~#
root@Pangolin:~# docker logs 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'

Starting migrations from version 1.1.0
Migrations to run:
All migrations completed successfully
2025-04-01T07:50:05.645Z [warn]: Email SMTP configuration is missing. Emails will not be sent.
2025-04-01T07:50:05.841Z [info]: Server admin (sir_kalot@yahoo.it) already exists
2025-04-01T07:50:06.165Z [info]: API server is running on http://localhost:3000
2025-04-01T07:50:06.165Z [info]: Internal server is running on http://localhost:3001
2025-04-01T07:50:06.671Z [info]: Next.js server is running on http://localhost:3002

the services are running well

# docker ps
CONTAINER ID   IMAGE                  COMMAND                  CREATED         STATUS                   PORTS                                                                                                                           NAMES
70f0ec612420   traefik:v3.3.3         "/entrypoint.sh --co…"   6 minutes ago   Up 6 minutes                                                                                                                                             traefik
d9ecd16777da   fosrl/gerbil:1.0.0     "/entrypoint.sh --re…"   6 minutes ago   Up 6 minutes             0.0.0.0:80->80/tcp, [::]:80->80/tcp, 0.0.0.0:443->443/tcp, [::]:443->443/tcp, 0.0.0.0:51820->51820/udp, [::]:51820->51820/udp   gerbil
304e125fd5a9   fosrl/pangolin:1.1.0   "docker-entrypoint.s…"   7 minutes ago   Up 6 minutes (healthy)                                                                                                                                   pangolin

but if I try to connect to the site https://pangolin.thisismysite.com the browser goes in timeout if I go to the local ip I get a page not found... :-(

More infos are that I've tested the address on dns and the nslookup gives me the right IP.
Any other ideas I could try to test where is the problem?

@pippo73 commented on GitHub (Apr 1, 2025): > Hello! > > What do you mean nothing happens? Do you get any errors in the browser? If so could you post them? > > Could you please also post your docker logs and remove anything you do not want shared? You can run `docker compose logs` I'm sorry yesterday it was really late for me and I was really disappointed 😥 Now I'm more fresh and I can be more "usefull" ``` # docker compose stop && docker system prune && docker compose up -d --remove-orphans --force-recreate [+] Stopping 3/3 ✔ Container traefik Stopped 0.1s ✔ Container gerbil Stopped 0.3s ✔ Container pangolin Stopped 5.2s WARNING! This will remove: - all stopped containers - all networks not used by at least one container - all dangling images - unused build cache Are you sure you want to continue? [y/N] y Deleted Containers: c7abeee8dc988e5452861c92bf9a2a81d1a47aa2d311679d5240e0a04fa45885 ffc0ac53df404afcbf93c7696205261c3ee62e17376884ac072cf3e40ce73dd9 d692c032b304b53d38384930656cc661d2c7328d480ece84027b93c4539591cd Deleted Networks: pangolin Total reclaimed space: 17.16kB [+] Running 4/4 ✔ Network pangolin Created 0.0s ✔ Container pangolin Healthy 22.9s ✔ Container gerbil Started 14.1s ✔ Container traefik Started ``` Hera are the logs ``` root@Pangolin:~# docker logs traefik 2025-04-01T07:50:07Z INF Traefik version 3.3.3 built on 2025-01-31T14:55:01Z version=3.3.3 2025-04-01T07:50:07Z 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-04-01T07:50:07Z INF Loading plugins... plugins=["badger"] 2025-04-01T07:50:08Z INF Plugins loaded. plugins=["badger"] 2025-04-01T07:50:08Z INF Starting provider aggregator *aggregator.ProviderAggregator 2025-04-01T07:50:08Z INF Starting provider *file.Provider 2025-04-01T07:50:08Z INF Starting provider *traefik.Provider 2025-04-01T07:50:08Z INF Starting provider *http.Provider 2025-04-01T07:50:08Z INF Starting provider *acme.ChallengeTLSALPN 2025-04-01T07:50:08Z INF Starting provider *acme.Provider 2025-04-01T07:50:08Z INF Testing certificate renew... acmeCA=https://acme-v02.api.letsencrypt.org/directory providerName=letsencrypt.acme root@Pangolin:~# root@Pangolin:~# root@Pangolin:~# docker logs gerbil INFO: 2025/04/01 07:50:07 Fetching remote config from http://pangolin:3001/api/v1/gerbil/get-config INFO: 2025/04/01 07:50:07 Created WireGuard interface wg0 INFO: 2025/04/01 07:50:07 Assigned IP address 100.89.128.1/24 to interface wg0 INFO: 2025/04/01 07:50:07 Attempting to delete existing MSS clamping rule for chain INPUT INFO: 2025/04/01 07:50:07 Attempting to delete existing MSS clamping rule for chain OUTPUT INFO: 2025/04/01 07:50:07 Attempting to delete existing MSS clamping rule for chain FORWARD INFO: 2025/04/01 07:50:07 Adding MSS clamping rule for chain INPUT INFO: 2025/04/01 07:50:07 Successfully added and verified MSS clamping rule for chain INPUT INFO: 2025/04/01 07:50:07 Adding MSS clamping rule for chain OUTPUT INFO: 2025/04/01 07:50:07 Successfully added and verified MSS clamping rule for chain OUTPUT INFO: 2025/04/01 07:50:07 Adding MSS clamping rule for chain FORWARD INFO: 2025/04/01 07:50:07 Successfully added and verified MSS clamping rule for chain FORWARD INFO: 2025/04/01 07:50:07 WireGuard interface wg0 created and configured INFO: 2025/04/01 07:50:07 Starting server on :3003 root@Pangolin:~# root@Pangolin:~# root@Pangolin:~# docker logs 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' Starting migrations from version 1.1.0 Migrations to run: All migrations completed successfully 2025-04-01T07:50:05.645Z [warn]: Email SMTP configuration is missing. Emails will not be sent. 2025-04-01T07:50:05.841Z [info]: Server admin (sir_kalot@yahoo.it) already exists 2025-04-01T07:50:06.165Z [info]: API server is running on http://localhost:3000 2025-04-01T07:50:06.165Z [info]: Internal server is running on http://localhost:3001 2025-04-01T07:50:06.671Z [info]: Next.js server is running on http://localhost:3002 ``` the services are running well ``` # docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 70f0ec612420 traefik:v3.3.3 "/entrypoint.sh --co…" 6 minutes ago Up 6 minutes traefik d9ecd16777da fosrl/gerbil:1.0.0 "/entrypoint.sh --re…" 6 minutes ago Up 6 minutes 0.0.0.0:80->80/tcp, [::]:80->80/tcp, 0.0.0.0:443->443/tcp, [::]:443->443/tcp, 0.0.0.0:51820->51820/udp, [::]:51820->51820/udp gerbil 304e125fd5a9 fosrl/pangolin:1.1.0 "docker-entrypoint.s…" 7 minutes ago Up 6 minutes (healthy) pangolin ``` but if I try to connect to the site https://pangolin.thisismysite.com the browser goes in timeout if I go to the local ip I get a page not found... :-( More infos are that I've tested the address on dns and the nslookup gives me the right IP. Any other ideas I could try to test where is the problem?
Author
Owner

@Lokowitz commented on GitHub (Apr 1, 2025):

Hi @pippo73,
did you open the ports 80, 443 and 51820/udp on your vps firewall?
If yes, could you also share your /config/traefik/dynamic_config.yml and /config/traefik/traefik_config.yml file?

Thanks

@Lokowitz commented on GitHub (Apr 1, 2025): Hi @pippo73, did you open the ports 80, 443 and 51820/udp on your vps firewall? If yes, could you also share your `/config/traefik/dynamic_config.yml` and `/config/traefik/traefik_config.yml` file? Thanks
Author
Owner

@pippo73 commented on GitHub (Apr 1, 2025):

The router is ok.
Here they are the files

# cat dynamic_config.yml
http:
  middlewares:
    redirect-to-https:
      redirectScheme:
        scheme: https

  routers:
    # HTTP to HTTPS redirect router
    main-app-router-redirect:
      rule: "Host(`pangolin.thisismysite.com`)"
      service: next-service
      entryPoints:
        - web
      middlewares:
        - redirect-to-https

    # Next.js router (handles everything except API and WebSocket paths)
    next-router:
      rule: "Host(`pangolin.thisismysite.com`) && !PathPrefix(`/api/v1`)"
      service: next-service
      entryPoints:
        - websecure
      tls:
        certResolver: letsencrypt

    # API router (handles /api/v1 paths)
    api-router:
      rule: "Host(`pangolin.thisismysite.com`) && PathPrefix(`/api/v1`)"
      service: api-service
      entryPoints:
        - websecure
      tls:
        certResolver: letsencrypt

    # WebSocket router
    ws-router:
      rule: "Host(`pangolin.thisismysite.com`)"
      service: api-service
      entryPoints:
        - websecure
      tls:
        certResolver: letsencrypt

  services:
    next-service:
      loadBalancer:
        servers:
          - url: "http://pangolin:3002"  # Next.js server

    api-service:
      loadBalancer:
        servers:
          - url: "http://pangolin:3000"  # API/WebSocket server

and the second

# cat traefik_config.yml
api:
  insecure: true
  dashboard: true

providers:
  http:
    endpoint: "http://pangolin:3001/api/v1/traefik-config"
    pollInterval: "5s"
  file:
    filename: "/etc/traefik/dynamic_config.yml"

experimental:
  plugins:
    badger:
      moduleName: "github.com/fosrl/badger"
      version: "v1.0.0"

log:
  level: "INFO"
  format: "common"

certificatesResolvers:
  letsencrypt:
    acme:
      httpChallenge:
        entryPoint: web
      email: "my mail ... ;-)"
      storage: "/letsencrypt/acme.json"
      caServer: "https://acme-v02.api.letsencrypt.org/directory"

entryPoints:
  web:
    address: ":80"
  websecure:
    address: ":443"
    transport:
      respondingTimeouts:
        readTimeout: "30m"
    http:
      tls:
        certResolver: "letsencrypt"

serversTransport:
  insecureSkipVerify: true

@pippo73 commented on GitHub (Apr 1, 2025): The router is ok. Here they are the files ``` # cat dynamic_config.yml http: middlewares: redirect-to-https: redirectScheme: scheme: https routers: # HTTP to HTTPS redirect router main-app-router-redirect: rule: "Host(`pangolin.thisismysite.com`)" service: next-service entryPoints: - web middlewares: - redirect-to-https # Next.js router (handles everything except API and WebSocket paths) next-router: rule: "Host(`pangolin.thisismysite.com`) && !PathPrefix(`/api/v1`)" service: next-service entryPoints: - websecure tls: certResolver: letsencrypt # API router (handles /api/v1 paths) api-router: rule: "Host(`pangolin.thisismysite.com`) && PathPrefix(`/api/v1`)" service: api-service entryPoints: - websecure tls: certResolver: letsencrypt # WebSocket router ws-router: rule: "Host(`pangolin.thisismysite.com`)" service: api-service entryPoints: - websecure tls: certResolver: letsencrypt services: next-service: loadBalancer: servers: - url: "http://pangolin:3002" # Next.js server api-service: loadBalancer: servers: - url: "http://pangolin:3000" # API/WebSocket server ``` and the second ``` # cat traefik_config.yml api: insecure: true dashboard: true providers: http: endpoint: "http://pangolin:3001/api/v1/traefik-config" pollInterval: "5s" file: filename: "/etc/traefik/dynamic_config.yml" experimental: plugins: badger: moduleName: "github.com/fosrl/badger" version: "v1.0.0" log: level: "INFO" format: "common" certificatesResolvers: letsencrypt: acme: httpChallenge: entryPoint: web email: "my mail ... ;-)" storage: "/letsencrypt/acme.json" caServer: "https://acme-v02.api.letsencrypt.org/directory" entryPoints: web: address: ":80" websecure: address: ":443" transport: respondingTimeouts: readTimeout: "30m" http: tls: certResolver: "letsencrypt" serversTransport: insecureSkipVerify: true ```
Author
Owner

@oschwartz10612 commented on GitHub (Apr 1, 2025):

Things look right so both of these issues make me think about firewalls. Are you 100% sure that the ports (443, 80) are open? Are you able to run a tcpdump on your VPS and see if any packets are making it when you visit the browser? If not you are not allowing packets through.

tcpdump -i any -n port 443

@oschwartz10612 commented on GitHub (Apr 1, 2025): Things look right so both of these issues make me think about firewalls. Are you 100% sure that the ports (443, 80) are open? Are you able to run a tcpdump on your VPS and see if any packets are making it when you visit the browser? If not you are not allowing packets through. `tcpdump -i any -n port 443`
Author
Owner

@pippo73 commented on GitHub (Apr 1, 2025):

That was I thought too... but my question is: why if connect to my internal IP nothing happens?
If I go to http://192.168.1.113 at least something should happend on the browser or in the logs...

@pippo73 commented on GitHub (Apr 1, 2025): That was I thought too... but my question is: why if connect to my internal IP nothing happens? If I go to http://192.168.1.113 at least something should happend on the browser or in the logs...
Author
Owner

@oschwartz10612 commented on GitHub (Apr 2, 2025):

Traefik uses the host header to detect how to route to different things so it expects the domain in the host header for requests. When you visit with the IP address the host header is the IP and it does not know what to do.

@oschwartz10612 commented on GitHub (Apr 2, 2025): Traefik uses the host header to detect how to route to different things so it expects the domain in the host header for requests. When you visit with the IP address the host header is the IP and it does not know what to do.
Author
Owner

@pippo73 commented on GitHub (Apr 3, 2025):

After long time spent with my ISP I've discovered that it was a problem of the network configuration of the router. Thanks for the help

@pippo73 commented on GitHub (Apr 3, 2025): After long time spent with my ISP I've discovered that it was a problem of the network configuration of the router. Thanks for the help
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#204