Website is not up

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:rocketchat.amepos.in

I ran this command:certbot certonly --nginx -d rocketchat.amepos.in

It produced this output: certificates are generated

My web server is (include version):nginx

The operating system my web server runs on is (include version):ubuntu

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know):yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):1.21.0

Hi! Your app tries to fetch https://143.244.133.13:3000/__meteor__/dynamic-import/fetch which fails due to CORS. Change ROOT_URL in your meteor runtime config to the url of your website.

5 Likes

Here is the certificate the site is presently serving https://decoder.link/sslchecker/rocketchat.amepos.in/443
Website seems up and running, maybe the content and configuration are not what you desire; but the certificate appears just fine.
And a nice rating here as well SSL Server Test: rocketchat.amepos.in (Powered by Qualys SSL Labs)

1 Like

Hi, i have changed in root_url still website is not up, rockatchat and mongod is active, but ip:port is up and running
i will share my nginx file

server {
    listen 80;
    server_name rocketchat.amepos.in;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;
    server_name rocketchat.amepos.in;
    ssl_certificate /etc/letsencrypt/live/rocketchat.amepos.in/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/rocketchat.amepos.in/privkey.pem;
    ssl_session_timeout 1d;
    ssl_session_cache shared:MozSSL:10m;  # about 40000 sessions
    ssl_session_tickets off;
    
    ssl_protocols TLSv1.2 TLSv1.3;
    ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384;
    ssl_prefer_server_ciphers off;
     # HSTS (ngx_http_headers_module is required) (63072000 seconds)
    add_header Strict-Transport-Security "max-age=63072000" always;

    ssl_trusted_certificate /etc/letsencrypt/live/rocketchat.amepos.in/chain.pem;

    # OCSP stapling
    ssl_stapling on;
    ssl_stapling_verify on;

    resolver 8.8.8.8 8.8.4.4 valid=300s;
    resolver_timeout 5s;

    location / {
        include proxy_params;
        proxy_pass http://127.0.0.1:3000;
    }

    error_page   500 502 503 504  /50x.html;
    location = /50x.html {
        root   /usr/share/nginx/html;
    }

    access_log /var/log/nginx/rocketchat.amepos.in.access;
    error_log /var/log/nginx/rocketchat.amepos.in.error;
}

Whatever you did was not enough, the app is still trying to fetch the same (wrong) url.

Since you got the certificate just fine and it's deployed correctly, anything else is outside of the scope of this forum. You would be better served by the documentation and support venues of the app you're trying to deploy.

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.