-
Notifications
You must be signed in to change notification settings - Fork 796
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
409 error when starting caprover on captain-nginx container #761
Comments
You nginx isn't running. Probably it is making your instance to restart. 1- Do you have any custom nginx configurations? |
no, i don't have custom nginx config applied as long as I remember. and when I logs captain-nginx the output is empty, no logs. i was wondering why is that... root@caprover-ubuntu-s-1vcpu-1gb-sgp1-01:~# docker service logs captain-nginx --since 10m
root@caprover-ubuntu-s-1vcpu-1gb-sgp1-01:~# docker service logs captain-nginx --since 60m
root@caprover-ubuntu-s-1vcpu-1gb-sgp1-01:~# docker service logs captain-nginx --since 60m --follow
^C
root@caprover-ubuntu-s-1vcpu-1gb-sgp1-01:~# here is user www-data;
worker_processes auto;
pid /run/nginx.pid;
include /etc/nginx/modules-enabled/*.conf;
events {
worker_connections 768;
# multi_accept on;
}
http {
##
# Basic Settings
##
sendfile on;
tcp_nopush on;
tcp_nodelay on;
keepalive_timeout 65;
types_hash_max_size 2048;
# server_tokens off;
# server_names_hash_bucket_size 64;
# server_name_in_redirect off;
include /etc/nginx/mime.types;
default_type application/octet-stream;
##
# SSL Settings
##
ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # Dropping SSLv3, ref: POODLE
ssl_prefer_server_ciphers on;
##
# Logging Settings
##
access_log /var/log/nginx/access.log;
error_log /var/log/nginx/error.log;
##
# Gzip Settings
##
gzip on;
# gzip_vary on;
# gzip_proxied any;
# gzip_comp_level 6;
# gzip_buffers 16 8k;
# gzip_http_version 1.1;
# gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript;
##
# Virtual Host Configs
##
include /etc/nginx/conf.d/*.conf;
include /etc/nginx/sites-enabled/*;
}
#mail {
# # See sample authentication script at:
# # http://wiki.nginx.org/ImapAuthenticateWithApachePhpScript
#
# # auth_http localhost/auth.php;
# # pop3_capabilities "TOP" "USER";
# # imap_capabilities "IMAP4rev1" "UIDPLUS";
#
# server {
# listen localhost:110;
# protocol pop3;
# proxy on;
# }
#
# server {
# listen localhost:143;
# protocol imap;
# proxy on;
# }
#} and no when I do root@caprover-ubuntu-s-1vcpu-1gb-sgp1-01:/captain/generated/nginx/conf.d# docker service scale captain-nginx=0
captain-nginx scaled to 0
overall progress: 0 out of 0 tasks
verify: Service converged
root@caprover-ubuntu-s-1vcpu-1gb-sgp1-01:/captain/generated/nginx/conf.d# docker service scale captain-nginx=1
captain-nginx scaled to 1
overall progress: 0 out of 1 tasks
1/1: preparing [=================================> ] |
You probably have another nginx that's sitting on your host and it's in conflict with the nginx. Either you, or a script that you used, started another nginx process. You have two options: 1- Simply start over from a brand new instance.
Is it providing any more info? |
I'm choosing to start over from new instance. Thanks for the help 🙏 |
if anyone has the same problem in the future related to nginx not running, run the following command to find out who is using port 443: and if it is apache2 on ubuntu, run: |
What is the problem?
Hi, after rebooting my machine, I cannot access my caprover dashboard port 3000. The ip and dns setting of my domain is fine. I can access my ip machine and give me nginx page in return. After doing troubleshooting on
https://caprover.com/docs/troubleshooting.html
I still got this error and my caprover still not running. I don't know is this docker issue, or caprover issue.What should I do to make my caprover running again?
Hereby I attach captain service logs below. Please kindly check.
Thank you
i don't understand, the container says its running but I can't access on port 3000 even with firewall sat up
The text was updated successfully, but these errors were encountered: