[GH-ISSUE #673] Access from Global via https is not working

kerem commented

2026-02-26 06:33:26 +03:00

Owner

Originally created by @GEkuL on GitHub (Oct 23, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/673

I've set up ampache server and connected it to domain via NPM. Everything was working without SSL: I could access the service from the Global.
After the turning SSL and trying https connection, the page doesn't show up. Yet without https connection from Global is still working fine.
Moreover https is working fine from the local network. But from the global the service is not uploading((((

Could you help me please!
Got the issue since the first installation of docker. Thought it's kind of bug. But it looks like the problem on my server. And I totally don't know what causes the problem.

Firewall is seemed to be disabled.
Possibly it could be the router, but I can't imagine how can it block SSL traffic directed to global internet...

Originally created by @GEkuL on GitHub (Oct 23, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/673 I've set up ampache server and connected it to domain via NPM. Everything was working without SSL: I could access the service from the Global. After the turning SSL and trying https connection, the page doesn't show up. Yet without https connection from Global is still working fine. Moreover https is working fine from the local network. But from the global the service is not uploading(((( Could you help me please! Got the issue since the first installation of docker. Thought it's kind of bug. But it looks like the problem on my server. And I totally don't know what causes the problem. Firewall is seemed to be disabled. Possibly it could be the router, but I can't imagine how can it block SSL traffic directed to global internet...

kerem closed this issue

2026-02-26 06:33:26 +03:00

kerem commented

2026-02-26 06:33:26 +03:00

Author

Owner

@Wadera commented on GitHub (Oct 27, 2020):

are you sure that you forwarding both ports on your router?
80 for http
443 for https

@Wadera commented on GitHub (Oct 27, 2020): are you sure that you forwarding both ports on your router? 80 for http 443 for https

kerem commented

2026-02-26 06:33:26 +03:00

Author

Owner

@GEkuL commented on GitHub (Oct 27, 2020):

@Wadera yeps
I'm forwarding both ports

Could it be some docker's settings since I use the NPM in container?

@GEkuL commented on GitHub (Oct 27, 2020): @Wadera yeps I'm forwarding both ports Could it be some docker's settings since I use the NPM in container?

kerem commented

2026-02-26 06:33:26 +03:00

Author

Owner

@Wadera commented on GitHub (Oct 28, 2020):

I think that everyone using NPM in docker container as that's how this tool is officially shipped ;)

make sure that you specified both ports under docker-compose.yml

Example docker composer config:
80: for http prox support
81: for NMP panel
443: for https proxy support
2500-3000: for forwarding ports for other applications under Streams

Of course you need to forward the same ports on your Router to your docker node machine IP

version: "3"
services:
  app:
    image: jc21/nginx-proxy-manager:latest
    restart: always
    ports:
      - 80:80
      - 81:81
      - 443:443
      - 2500-3000:2500-3000/tcp
      - 2500-3000:2500-3000/udp
    volumes:
      - /somewhere/on/your/local/storage/proxy/config.json:/app/config/production.json
      - /somewhere/on/your/local/storage/proxy/data:/data
      - /somewhere/on/your/local/storage/proxy/letsencrypt:/etc/letsencrypt
    depends_on:
      - db
    environment:
    # if you want pretty colors in your docker logs:
    - FORCE_COLOR=1
  db:
    image: mariadb:latest
    restart: always
    environment:
      MYSQL_ROOT_PASSWORD: "yoursecretroodpassword"
      MYSQL_DATABASE: "npm"
      MYSQL_USER: "npm"
      MYSQL_PASSWORD: "yoursecretpassword"
    volumes:
      - /somewhere/on/your/local/storage/proxy/data/mysql:/var/lib/mysql

And then to start:

# docker-compose up -d

Of if you rewrite your already existing docker compose config:

# docker-compose down && docker-compose up -d

@Wadera commented on GitHub (Oct 28, 2020): I think that everyone using NPM in docker container as that's how this tool is officially shipped ;) make sure that you specified both ports under `docker-compose.yml` **Example docker composer config:** **80:** for http prox support **81:** for NMP panel **443:** for https proxy support **2500-3000:** for forwarding ports for other applications under Streams Of course you need to forward the same ports on your Router to your docker node machine IP ``` version: "3" services: app: image: jc21/nginx-proxy-manager:latest restart: always ports: - 80:80 - 81:81 - 443:443 - 2500-3000:2500-3000/tcp - 2500-3000:2500-3000/udp volumes: - /somewhere/on/your/local/storage/proxy/config.json:/app/config/production.json - /somewhere/on/your/local/storage/proxy/data:/data - /somewhere/on/your/local/storage/proxy/letsencrypt:/etc/letsencrypt depends_on: - db environment: # if you want pretty colors in your docker logs: - FORCE_COLOR=1 db: image: mariadb:latest restart: always environment: MYSQL_ROOT_PASSWORD: "yoursecretroodpassword" MYSQL_DATABASE: "npm" MYSQL_USER: "npm" MYSQL_PASSWORD: "yoursecretpassword" volumes: - /somewhere/on/your/local/storage/proxy/data/mysql:/var/lib/mysql ``` And then to start: ``` # docker-compose up -d ``` Of if you rewrite your already existing docker compose config: ``` # docker-compose down && docker-compose up -d ```

kerem commented

2026-02-26 06:33:26 +03:00

Author

Owner

@GEkuL commented on GitHub (Oct 28, 2020):

2500-3000: for forwarding ports for other applications under Streams

Am I right that if i want to set up a https connection for my Ampache server I don't need those ports, since the fact that all the traftic is going through the 443 port in this case?

@GEkuL commented on GitHub (Oct 28, 2020): > **2500-3000:** for forwarding ports for other applications under Streams Am I right that if i want to set up a https connection for my Ampache server I don't need those ports, since the fact that all the traftic is going through the 443 port in this case?

kerem commented

2026-02-26 06:33:26 +03:00

Author

Owner

@GEkuL commented on GitHub (Oct 28, 2020):

Of if you rewrite your already existing docker compose config:
# docker-compose down && docker-compose up -d

Could it be the problem that I'm making docker-compose with sudo?
docker commands can only be used with it on my machine
or should I reinstall the docker in some kind of proper way?

@GEkuL commented on GitHub (Oct 28, 2020): > Of if you rewrite your already existing docker compose config: > > ``` > # docker-compose down && docker-compose up -d > ``` Could it be the problem that I'm making docker-compose with sudo? docker commands can only be used with it on my machine or should I reinstall the docker in some kind of proper way?

kerem commented

2026-02-26 06:33:27 +03:00

Author

Owner

@Wadera commented on GitHub (Oct 28, 2020):

Yes, docker command need to be run by root or with sudo as standard user.
And correct - if you just need standard apache app then port 80 and 443 should be enough.

@Wadera commented on GitHub (Oct 28, 2020): Yes, docker command need to be run by root or with sudo as standard user. And correct - if you just need standard apache app then port 80 and 443 should be enough.

kerem commented

2026-02-26 06:33:27 +03:00

Author

Owner

@GEkuL commented on GitHub (Oct 28, 2020):

I think that everyone using NPM in docker container as that's how this tool is officially shipped ;)

make sure that you specified both ports under docker-compose.yml

Example docker composer config:
80: for http prox support
81: for NMP panel
443: for https proxy support
2500-3000: for forwarding ports for other applications under Streams

Of course you need to forward the same ports on your Router to your docker node machine IP
version: "3"
services:
  app:
    image: jc21/nginx-proxy-manager:latest
    restart: always
    ports:
      - 80:80
      - 81:81
      - 443:443
      - 2500-3000:2500-3000/tcp
      - 2500-3000:2500-3000/udp
    volumes:
      - /somewhere/on/your/local/storage/proxy/config.json:/app/config/production.json
      - /somewhere/on/your/local/storage/proxy/data:/data
      - /somewhere/on/your/local/storage/proxy/letsencrypt:/etc/letsencrypt
    depends_on:
      - db
    environment:
    # if you want pretty colors in your docker logs:
    - FORCE_COLOR=1
  db:
    image: mariadb:latest
    restart: always
    environment:
      MYSQL_ROOT_PASSWORD: "yoursecretroodpassword"
      MYSQL_DATABASE: "npm"
      MYSQL_USER: "npm"
      MYSQL_PASSWORD: "yoursecretpassword"
    volumes:
      - /somewhere/on/your/local/storage/proxy/data/mysql:/var/lib/mysql
And then to start:
# docker-compose up -d
Of if you rewrite your already existing docker compose config:
# docker-compose down && docker-compose up -d

didn't work :(
One more question:
Should the Scheme in Details tab of Proxy Host be specified as http or https?

@GEkuL commented on GitHub (Oct 28, 2020): > I think that everyone using NPM in docker container as that's how this tool is officially shipped ;) > > make sure that you specified both ports under `docker-compose.yml` > > **Example docker composer config:** > **80:** for http prox support > **81:** for NMP panel > **443:** for https proxy support > **2500-3000:** for forwarding ports for other applications under Streams > > Of course you need to forward the same ports on your Router to your docker node machine IP > > ``` > version: "3" > services: > app: > image: jc21/nginx-proxy-manager:latest > restart: always > ports: > - 80:80 > - 81:81 > - 443:443 > - 2500-3000:2500-3000/tcp > - 2500-3000:2500-3000/udp > volumes: > - /somewhere/on/your/local/storage/proxy/config.json:/app/config/production.json > - /somewhere/on/your/local/storage/proxy/data:/data > - /somewhere/on/your/local/storage/proxy/letsencrypt:/etc/letsencrypt > depends_on: > - db > environment: > # if you want pretty colors in your docker logs: > - FORCE_COLOR=1 > db: > image: mariadb:latest > restart: always > environment: > MYSQL_ROOT_PASSWORD: "yoursecretroodpassword" > MYSQL_DATABASE: "npm" > MYSQL_USER: "npm" > MYSQL_PASSWORD: "yoursecretpassword" > volumes: > - /somewhere/on/your/local/storage/proxy/data/mysql:/var/lib/mysql > ``` > > And then to start: > > ``` > # docker-compose up -d > ``` > > Of if you rewrite your already existing docker compose config: > > ``` > # docker-compose down && docker-compose up -d > ``` didn't work :( One more question: Should the Scheme in Details tab of Proxy Host be specified as http or https?

kerem commented

2026-02-26 06:33:27 +03:00

Author

Owner

@Wadera commented on GitHub (Oct 28, 2020):

So - the best to make it https to https

NPM Proxy scheme set for https
Hosting in backed need to be available under https as well (can have self-signed cert - IT will be override by NPM anyway)

@Wadera commented on GitHub (Oct 28, 2020): So - the best to make it https to https NPM Proxy scheme set for https Hosting in backed need to be available under https as well (can have self-signed cert - IT will be override by NPM anyway)

kerem commented

2026-02-26 06:33:27 +03:00

Author

Owner

@GEkuL commented on GitHub (Oct 28, 2020):

@Wadera it really looks like the problem with the router. Do you know any kind of protecting mechanics in routers?
I disables firewall SPI, but nothing changed. There must be another problem(

@GEkuL commented on GitHub (Oct 28, 2020): @Wadera it really looks like the problem with the router. Do you know any kind of protecting mechanics in routers? I disables firewall SPI, but nothing changed. There must be another problem(

kerem commented

2026-02-26 06:33:27 +03:00

Author

Owner

@GEkuL commented on GitHub (Jan 9, 2021):

Solution found.

It seems like the problem is in provider. Because on another one everything is working.

So if you got the same issue, check up firewall and the provider first. :)

@GEkuL commented on GitHub (Jan 9, 2021): Solution found. It seems like the problem is in provider. Because on another one everything is working. So if you got the same issue, check up firewall and the provider first. :)

kerem referenced this issue

2026-02-26 07:38:40 +03:00

[PR #570] [MERGED] Bump bcrypt from 4.0.1 to 5.0.0 in /backend #3266

Rows
Columns

[GH-ISSUE #673] Access from Global via https is not working #570