search

jlesage / docker-nginx-proxy-manager

Docker container for Nginx Proxy Manager
MIT License
780 stars 176 forks source link

Are there some "methods" in new version of nginx that causes this error? And Proxy Hosts also displays the error. #64

Open xiaodinghoney opened 4 years ago

xiaodinghoney commented 4 years ago

[app] starting Nginx Proxy Manager... [4/8/2020] [10:21:02 PM] [Migrate ] › ℹ info Current database version: 20190227065017

[4/8/2020] [10:21:02 PM] [Setup ] › ℹ info Creating a new user: admin@example.com with password: changeme [4/8/2020] [10:21:02 PM] [Setup ] › ℹ info Initial setup completed [4/8/2020] [10:21:02 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [4/8/2020] [10:21:02 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [4/8/2020] [10:21:07 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4 [4/8/2020] [10:21:09 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6 [4/8/2020] [10:21:11 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized [4/8/2020] [10:21:11 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry... [4/8/2020] [10:21:11 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [4/8/2020] [10:21:11 PM] [Global ] › ℹ info Backend PID 961 listening on port 3000 ... [4/8/2020] [10:21:11 PM] [Nginx ] › ℹ info Reloading Nginx [4/8/2020] [10:21:11 PM] [SSL ] › ℹ info Renew Complete QueryBuilder#allowEager method is deprecated. You should use allowGraph instead. allowEager method will be removed in 3.0 QueryBuilder#eager method is deprecated. You should use the withGraphFetched method instead. eager method will be removed in 3.0 QueryBuilder#omit is deprecated. This method will be removed in version 3.0

[4/8/2020] [10:21:48 PM] [Nginx ] › ℹ info Reloading Nginx [4/8/2020] [10:22:16 PM] [Nginx ] › ℹ info Reloading Nginx [4/8/2020] [10:22:17 PM] [Nginx ] › ℹ info Reloading Nginx [4/8/2020] [10:23:08 PM] [Nginx ] › ℹ info Reloading Nginx

In the webUI , Audit log.

{ "id": 1, "created_on": "2020-04-08T14:21:48.000Z", "modified_on": "2020-04-08T14:22:17.000Z", "owner_user_id": 1, "domain_names": [ "xxx.abc.com" ], "forward_host": "192.168.30.1", "forward_port": 80, "access_list_id": 0, "certificate_id": 1, "ssl_forced": true, "caching_enabled": false, "block_exploits": false, "advanced_config": "", "meta": { "nginx_online": false, "nginx_err": "Command failed: /usr/sbin/nginx -t \nnginx: the configuration file /etc/nginx/nginx.conf syntax is ok\nnginx: [emerg] bind() to [::]:80 failed (13: Permission denied)\nnginx: configuration file /etc/nginx/nginx.conf test failed\n" }, "allow_websocket_upgrade": false, "http2_support": false, "forward_scheme": "http", "enabled": 1, "locations": [], "hsts_enabled": false, "hsts_subdomains": false }

mdisieno commented 4 years ago

I just got the same issue on v2.2.2 on my VPS. My home machine which was previously 2.2.1 was working great, and now since updating to 2.2.2 if I add anything its offline with the same issue. I've noticed the tags do not show 2.2.1 available as it goes straight from 1.7.3 to latest.

xiaodinghoney commented 4 years ago

I just got the same issue on v2.2.2 on my VPS. My home machine which was previously 2.2.1 was working great, and now since updating to 2.2.2 if I add anything its offline with the same issue. I've noticed the tags do not show 2.2.1 available as it goes straight from 1.7.3 to latest.

yes. me too.

SuberSeb commented 4 years ago

Same issue here.

SuberSeb commented 4 years ago

I have successfully installed 2.2.1 version which is working fine. 1.7.2 tag is actually 2.2.1 version of Nginx Proxy Manager. But you need to delete config folder with all proxies, domains, settings, etc. Only installing 2.2.1 doesn't solve the issue, you need to delete configs. 2.2.1 working fine, seems like 2.2.2 version bug.

mdisieno commented 4 years ago

If I may ask, how did you install 2.2.1 of jlesage/nginx-proxy-manager? The tags on dockerhub show latest and then 1.7.3.

SuberSeb commented 4 years ago

If I may ask, how did you install 2.2.1 of jlesage/nginx-proxy-manager? The tags on dockerhub show latest and then 1.7.3.

Docker hub tag and Nginx Proxy Manager version is not the same. 1.7.2 tag on docker hub is actually 2.2.1 version of Nginx Proxy Manager.

mdisieno commented 4 years ago

AH nice! thank you!

NeoMatrixJR commented 4 years ago

Tagging with a "same"... +1 on this issue

mdisieno commented 4 years ago

Can confirm, 1.7.2 is 2.2.1 and it works great. Didnt even have to wipe my configs.

Reftek85 commented 4 years ago

same problem here on Unraid, upgraded to 2.2.2 and everything gives me internal error. is there a way on unraid to install 2.2.1?

SuberSeb commented 4 years ago

same problem here on Unraid, upgraded to 2.2.2 and everything gives me internal error. is there a way on unraid to install 2.2.1?

Of course. I'm using unraid, just install image with 1.7.2 tag.

Reftek85 commented 4 years ago

first time doing, this can you tell me where to input the 1.7.2 tag?

mdisieno commented 4 years ago

@Reftek85 when you do the pull, pull jlesage/nginx-proxy-manager:v1.7.2

Reftek85 commented 4 years ago

thank you for you help i got it to download the good version!

jlesage commented 4 years ago

This is now fixed with the latest image.

To fix the offline proxy hosts, just edit them and save.

BenHall-1 commented 4 years ago

Check #65 for the fix