Accidently Deleted SSL Certifiacte

[Bruce5051]

@DepressionCherry

nginx: configuration file /etc/nginx/nginx.conf test failed

You need to get that fixed and working.

[Osiris]

That's the whole issue this thread is all about Bruce..

OP simply needs to either remove/comment out the HTTPS server block or change the SSL directives to the snake oil certs temporarily.

[Bruce5051]

@Osiris

That's the whole issue this thread

I am not sure the OP knows that.

[DepressionCherry]

So do I need to do that here /etc/nginx/nginx.conf or /etc/nginx/sites-enabled/default because I don't see the server blocks on the .conf and I don't know if it that matters or not

[schoen]

This exact part is what needs to be deleted in order to be able to restart nginx:

@DepressionCherry

server {

       # SSL configuration
       #
       # listen 443 ssl default_server;
       # listen [::]:443 ssl default_server;
       #
       # Note: You should disable gzip for SSL traffic.
       # See: https://bugs.debian.org/773332
       #
       # Read up on ssl_ciphers to ensure a secure configuration.
       # See: https://bugs.debian.org/765782
       #
       # Self signed certs generated by the ssl-cert package
       # Don't use them in a production server!
       #
       # include snippets/snakeoil.conf;

       root /var/www/html;

       # Add index.php to the list if you are using PHP
       index index.html index.htm index.nginx-debian.html;
   server_name www.filehb.tech filehb.tech; # managed by Certbot


       location / {
               # First attempt to serve request as file, then
               # as directory, then fall back to displaying a 404.
               try_files $uri $uri/ =404;
       }

       # pass PHP scripts to FastCGI server
       #
       #location ~ \.php$ {
       #       include snippets/fastcgi-php.conf;
       #
       #       # With php-fpm (or other unix sockets):
       #       fastcgi_pass unix:/run/php/php7.4-fpm.sock;
       #       # With php-cgi (or other tcp sockets):
       #       fastcgi_pass 127.0.0.1:9000;
       #}

       # deny access to .htaccess files, if Apache's document root
       # concurs with nginx's one
       #
       #location ~ /\.ht {
       #       deny all;
       #}


   listen [::]:443 ssl ipv6only=on; # managed by Certbot
   listen 443 ssl; # managed by Certbot
   ssl_certificate /etc/letsencrypt/live/filehb.tech/fullchain.pem; # managed by Certbot
   ssl_certificate_key /etc/letsencrypt/live/filehb.tech/privkey.pem; # managed by Certbot
   include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
   ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot



}
server {
   if ($host = www.filehb.tech) {
       return 301 https://$host$request_uri;
   } # managed by Certbot


   if ($host = filehb.tech) {
       return 301 https://$host$request_uri;
   } # managed by Certbot
  
   listen 80 ;
       listen [::]:80 ;
   server_name www.filehb.tech filehb.tech;
   return 404; # managed by Certbot




}

[DepressionCherry]

Fixed it had to create the path /etc/letsencrypt/live/filehb.tech/ because it got deleted from there I had to run sudo certbot certonly --standalone -d filehb.tech which successfully gave me a new certificate. Then, I had to Generate DH Parameters with sudo openssl dhparam -out /etc/letsencrypt/ssl-dhparams.pem 2048. Finally after that, I just had to update and restart nginx and everything is working again. Thank you to everyone for trying to help I learned a lot from this

[rg305]

@DepressionCherry

Then, I had to Generate DH Parameters

I'm curious... Why do you still use DH params?
[you might do better by switching from RSA to ECDSA type certs]

[DepressionCherry]

Since this is a group project I guess the person who set it up initially had it that way because in the /sites-available/default file it had ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot and Nginx was unable to find this file in the specified location (/etc/letsencrypt/) so that's why I had to generate DH Parameters

[rg305]

@DepressionCherry

the person who set it up initially had it that way

Well, by that logic it will never go away - LOL