New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to connect ANY clients to NEXTCLOUD behind NGINX Reverse Proxy #2203
Comments
Several things i see wrong with this setup, i will try to address them as much as i can. Proxy: Nginx configuration , click to expand
Nextcloud setup: Also, I would suggest not opening the database port. Click to expand this exampleservices:
db:
image: mariadb:10.6
command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW
restart: always
volumes:
- db:/var/lib/mysql
environment:
- MYSQL_ROOT_PASSWORD=
- MARIADB_AUTO_UPGRADE=1
- MARIADB_DISABLE_UPGRADE_BACKUP=1
redis:
image: redis:alpine
restart: always
app:
image: nextcloud:apache
restart: always
ports:
- 127.0.0.1:8080:80
volumes:
- nextcloud:/var/www/html
environment:
- MYSQL_HOST=db
- REDIS_HOST=redis
depends_on:
- db
- redis
cron:
image: nextcloud:apache
restart: always
volumes:
- nextcloud:/var/www/html
entrypoint: /cron.sh
depends_on:
- db
- redis
volumes:
db:
nextcloud: I would get rid of watchtower container if you don't know what exactly is doing and what problems it can create. It's good to have, but only in specific scenarios. Also, I am assuming you are using valid certificates. Invalid such will cause problems with most browsers, unless you explicitly allow them / add them to the certificate stores of said browsers. |
Thank you so much for the reply. I will try out the NGINX Proxy Manager that I have been hearing about. It is a container as well. Thank you for the updated docker-compose file. I try your suggestions and try this again. LEARNING IS HARD :-( ROFL |
also, yes the certificates are valid and from LetsEncrypt |
As a guide ( Iwrote this a while ago, and I'm unsure on how accurate it is) you can use this https://github.com/tzerber/docker_nc_psql_nginx_ssl Screenshots there will help with nginx-proxy-manager for sure. |
Hi @TacitTactics! Can you post your query on the Help Forum (https://help.nextcloud.com)? This channel is for bug reporting in the image itself and this seems to be a general troubleshooting matter.
Well, it's closer because you'd like clients to be directed to your external https:// proxy, correct? :) What are your other https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/config_sample_php_parameters.html#proxy-configurations |
Your container is actually listening on 8080 per your config so it's accurate based on what you've told Nextcloud so far. Keep in mind there are additional overwrite* parameters you will likely need to set, such as the external hostname and port. The overwrite* parameters are all about telling Nextcloud what your externally visible HTTPS host is reachable at. That is presumably, in your case, your outermost reverse proxy that you labeled Reverse Proxy (NGINX) in VPS. Use the hostname of the Nextcloud vhost on it, its associated port, protocol, etc. See the Reverse Proxy section of the Nextcloud Admin Manual (https://docs.nextcloud.com) as well as the Docker specific notes here in this repository's README. I'm going to close this since there isn't anything actionable here for us to do in the image itself. But do feel free to follow-up at the [Community Help Forum] Hope that helps. |
I am new to using docker. I have searched for hours and it seems that my issues was resolved years ago, but the solutions are not working for me.
My setup:
Reverse Proxy (NGINX) in VPS -> Reverse Proxy (NGINX) internally -> Reverse Proxy (NGINX) on host running NEXTCloud.
NGINX config:
Nextcloud setup:
OS ==> Ubuntu Lite OS 64 on Raspberry PI 5
executing using docker-compose file:
Scenario 1:
Run as is, web browser works just fine,but Windows, LINUX, and Android clients all fail. The windows and Linux clients
If I use online solution of adding the following lines to config/config.php:
Then all clients are redirected to "https://localhost:8080" but this is just wrong because the docker is only listening on 80 http.
Please help... if logs are needed, please leave steps on how to retrieve them so I can provide them. Thank you.
The text was updated successfully, but these errors were encountered: