Homer-S
-
Posts
10 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Homer-S
-
-
Hello,
I have faced issues with my nextcloud setup. My container runs according the tutorial behind a reverese proxy:
This is the entry in my error log:
2017/05/19 23:30:44 [crit] 338#338: *827 open() "/var/lib/nginx/tmp/proxy/8/01/0000000018" failed (13: Permission denied) while reading upstream, client: 87.174.234.100, server: nextcloud.homer-s.my-wan.de, request: "GET /apps/files_texteditor/js/core/vendor/ace-builds/src-noconflict/ace.js?v=888e4165f3921f766e1898594559ec7b HTTP/1.1", upstream: "https://192.168.100.10:4432/apps/files_texteditor/js/core/vendor/ace-builds/src-noconflict/ace.js?v=888e4165f3921f766e1898594559ec7b", host: "nextcloud.homer-s.my-wan.de"
2017/05/19 23:30:44 [crit] 338#338: *827 open() "/var/lib/nginx/tmp/proxy/8/01/0000000018" failed (13: Permission denied) while reading upstream, client: 87.174.234.100, server: nextcloud.myserver.de, request: "GET /apps/files_texteditor/js/core/vendor/ace-builds/src-noconflict/ace.js?v=888e4165f3921f766e1898594559ec7b HTTP/1.1", upstream: "https://192.168.100.10:4432/apps/files_texteditor/js/core/vendor/ace-builds/src-noconflict/ace.js?v=888e4165f3921f766e1898594559ec7b", host: "nextcloud.myserver.de"any idea what to do?
-
Hello,
another question (not related to reverse proxying
I received an email from letsencrypt that my man URI will expire within 9 days.
I exec then letsencrypt container with bash /app/le-renew.sh by hand and it tells me
The following certs are not due for renewal yet: /path/path/path/fullchain.pem
The option subdomain only is set to false.
Do you have any idea?
-
oh, I am sorry.
Thanks in advance for your help!!!
-
4 minutes ago, CHBMB said:
@Homer-S Are you using Unraid?
No, ubuntu server 16.04
-
He comes my Pydio config
server { listen 443 ssl; server_name pydio.dyndns.myserver.com; root /config/www; index index.html index.htm index.php; access_log /config/log/nginx/access_pydio.log; error_log /config/log/nginx/error_pydio.log; ###SSL Certificates ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ###Diffie–Hellman key exchange ### ssl_dhparam /config/nginx/dhparams.pem; ###SSL Ciphers ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ###Extra Settings### ssl_prefer_server_ciphers on; ssl_session_cache shared:SSL:10m; ### Add HTTP Strict Transport Security ### add_header Strict-Transport-Security "max-age=63072000; includeSubdomains"; add_header Front-End-Https on; client_max_body_size 0; location / { proxy_pass http://192.168.1.11:84/; } }Now back to my wordpress issue.
This is the official container from wordpress:
docker run -it -d \ --name wordpress \ --restart=always \ -p 90:80 \ -e PUID=33 -e PGID=33 \ -e TZ=Europe/Berlin \ -v /docker/data/wordpress:/var/www/html \ wordpressit is working with local ip 192.168.1.11:90
mariadb is successfully set up with wordpress db
if I am going to access it via nginx reverse proxy
I am entering this
and this is after a short time displayed in url bar:
subdomain:90
and a "server not found" page appears.
this is my wordpress config file:
server { listen 443 ssl; server_name wordpress.dyndns.myserver.com; root /config/www; index index.html index.htm index.php; access_log /config/log/nginx/access_wordpress.log; error_log /config/log/nginx/error_wordpress.log; ###SSL Certificates ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ###Diffie–Hellman key exchange ### ssl_dhparam /config/nginx/dhparams.pem; ###SSL Ciphers ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ###Extra Settings### ssl_prefer_server_ciphers on; ssl_session_cache shared:SSL:10m; ### Add HTTP Strict Transport Security ### add_header Strict-Transport-Security "max-age=63072000; includeSubdomains"; add_header Front-End-Https on; client_max_body_size 0; location / { proxy_pass http://192.168.1.11:90/; } } -
Hello,
after solving issues with Pydio I am facing strange things with a wordpress container which should be accessed similar.
I am using same conf file as for pydio/nextcloud for wordpress.
localhost access is working perfectly.
if I am adding subdomain.myserver.de browsertools show me a address like this
subdomain:90
90 is the port I want to forward to but I can not figure out why it is not using my proxy_pass http://192.168.100.10:90/; command?
Does anybody has an idea what is wrong or a working nginx-rev-proxy-config for wordpress container?
many thanks, and I am promising, after that my whole server is setup completely
-
6 hours ago, Malykai said:
Homer-S, can you include the rest of the error? A lot of the time that error is pointing out an incorrect IP but that part doesn't seem to be included here.Sorry, for sure I can.QuoteSSL_do_handshake() failed (SSL: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol) while SSL handshaking to upstream, client: XX.174.239.197, server: pydio.XX.myadress.de, request: "GET / HTTP/1.1", upstream: "https://192.168.100.10:84/", host: "pydio.XX.myadress.de"Is there a way to check if all three subdomains are included in keys?I found my mistake!!!
wrong:
proxy_pass https://192.168.100.10:84/;
correct:
proxy_pass http://192.168.100.10:84/;
That was the reason for SSL error
Thanks anyway
-
Hello
I created letsencrypt container with 3 different subdomains (pydio and nextcloud included). Then I followed latest article to run nextcloud behind nginx reverese proxy.
for nextcloud it is working
but with pydio (2 different config files)
it fails with :
SSL_do_handshake() failed (SSL: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown ....I am wondering how you differ the subdomain keys? Because in keys folder is only a link to one folder mydomain.com
and in config file we have these lines each:
ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem;do I have to do something different?
Thank
[Support] Linuxserver.io - Nextcloud
in Docker Containers
Posted
Sorry,
I had issues with creating new users and iPhone app created some errors. So I thought this error message could be the reason.
In the meanwhile I found a way to change path for tmp path and error message is gone.
User creating issue was a simple settings error (allow common passwords) but nextcloud do not show you an error just doing nothing ... solved so far.
But many thanks anyway, you guys doing a great job!