sudo systemctl status postgresql
* postgresql.service - PostgreSQL RDBMS
Loaded: loaded (/lib/systemd/system/postgresql.service; enabled; vendor pr>
Active: active (exited) since Fri 2023-03-03 20:02:47 MSK; 39min ago
Process: 21310 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
Main PID: 21310 (code=exited, status=0/SUCCESS)
Mar 03 20:02:47 vm2179144 systemd[1]: Starting PostgreSQL RDBMS...
Mar 03 20:02:47 vm2179144 systemd[1]: Finished PostgreSQL RDBMS.
lines 1-8/8 (END)root@vm2101602:~# sudo nginx -T
nginx: [emerg] open() "/etc/nginx/ssl.conf" failed (2: No such file or directory) in /etc/nginx/sites-enabled/default:25
nginx: configuration file /etc/nginx/nginx.conf test failedroot@vm2101602:~# systemctl status nginx
● nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: en
Active: failed (Result: exit-code) since Thu 2023-01-05 07:24:35 EST; 17s ago
Process: 7691 ExecStop=/sbin/start-stop-daemon --quiet --stop --retry QUIT/5 -
Process: 7685 ExecReload=/usr/sbin/nginx -g daemon on; master_process on; -s r
Process: 280 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=
Process: 7721 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process
Main PID: 297 (code=exited, status=0/SUCCESS)
Jan 05 07:24:35 vm2101602 systemd[1]: Starting A high performance web server and
Jan 05 07:24:35 vm2101602 nginx[7721]: nginx: [emerg] open() "/etc/nginx/ssl.con
Jan 05 07:24:35 vm2101602 nginx[7721]: nginx: configuration file /etc/nginx/ngin
Jan 05 07:24:35 vm2101602 systemd[1]: nginx.service: Control process exited, cod
Jan 05 07:24:35 vm2101602 systemd[1]: Failed to start A high performance web ser
Jan 05 07:24:35 vm2101602 systemd[1]: nginx.service: Unit entered failed state.
Jan 05 07:24:35 vm2101602 systemd[1]: nginx.service: Failed with result 'exit-co
lines 1-16/16 (END)root@vm2101602:~# sudo certbot certonly --webroot --agree-tos --email givenmudus23@gmail.com -w /var/www/cert_bot/ -d vk-king-games.ru
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Would you be willing to share your email address with the Electronic Frontier
Foundation, a founding partner of the Let's Encrypt project and the non-profit
organization that develops Certbot? We'd like to send you email about our work
encrypting the web, EFF news, campaigns, and ways to support digital freedom.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(Y)es/(N)o: y
Starting new HTTPS connection (1): supporters.eff.org
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for vk-king-games.ru
Using the webroot path /var/www/cert_bot for all unmatched domains.
Waiting for verification...
Cleaning up challenges
IMPORTANT NOTES:
- Congratulations! Your certificate and chain have been saved at:
/etc/letsencrypt/live/vk-king-games.ru/fullchain.pem
Your key file has been saved at:
/etc/letsencrypt/live/vk-king-games.ru/privkey.pem
Your cert will expire on 2023-04-05. To obtain a new or tweaked
version of this certificate in the future, simply run certbot
again. To non-interactively renew *all* of your certificates, run
"certbot renew"
- Your account credentials have been saved in your Certbot
configuration directory at /etc/letsencrypt. You should make a
secure backup of this folder now. This configuration directory will
also contain certificates and private keys obtained by Certbot so
making regular backups of this folder is ideal.
- If you like Certbot, please consider supporting our work by:
Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate
Donating to EFF: https://eff.org/donate-lesudo reboot, это уже в гугле нашел.sudo certbot certonly --dry-run --webroot --agree-tos --email givenmudus23@gmail.com -w /var/www/cert_bot/ -d vk-king-games.ruSaving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Starting new HTTPS connection (1): acme-staging-v02.api.letsencrypt.org
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for vk-king-games.ru
Using the webroot path /var/www/cert_bot for all unmatched domains.
Waiting for verification...
Cleaning up challenges
IMPORTANT NOTES:
- The dry run was successful.
- Your account credentials have been saved in your Certbot
configuration directory at /etc/letsencrypt. You should make a
secure backup of this folder now. This configuration directory will
also contain certificates and private keys obtained by Certbot so
making regular backups of this folder is ideal.E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?root@vm2101602:~# sudo certbot certonly --dry-run --webroot --agree-tos --email givenmudus23@gmail.com -w /var/www/cert_bot/ -d vk-king-games.ru
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Starting new HTTPS connection (1): acme-staging-v02.api.letsencrypt.org
An unexpected error occurred:
SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)
Please see the logfiles in /var/log/letsencrypt for more details.root@vm2101602:~# sudo certbot certonly --dry-run --webroot --agree-tos --email givenmudus23@gmail.com -w /var/www/cert_bot/ -d vk-king-games.ru
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Starting new HTTPS connection (1): acme-staging-v02.api.letsencrypt.org
An unexpected error occurred:
SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)
Please see the logfiles in /var/log/letsencrypt for more details.##
# You should look at the following URL's in order to grasp a solid understanding
# of Nginx configuration files in order to fully unleash the power of Nginx.
# http://wiki.nginx.org/Pitfalls
# http://wiki.nginx.org/QuickStart
# http://wiki.nginx.org/Configuration
#
# Generally, you will want to move this file somewhere, and start with a clean
# file but keep this around for reference. Or just disable in sites-enabled.
#
# Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.
##
# Default server configuration
#
server {
listen 80 default_server;
listen [::]:80 default_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 _;
location / {
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 404.
try_files $uri $uri/ =404;
}
# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
#
#location ~ \.php$ {
# include snippets/fastcgi-php.conf;
#
# # With php7.0-cgi alone:
# fastcgi_pass 127.0.0.1:9000;
# # With php7.0-fpm:
# fastcgi_pass unix:/run/php/php7.0-fpm.sock;
#}
# deny access to .htaccess files, if Apache's document root
# concurs with nginx's one
#
#location ~ /\.ht {
# deny all;
#}
}
# Virtual Host configuration for example.com
#
# You can move that to a different file under sites-available/ and symlink that
# to sites-enabled/ to enable it.
#
#server {
# listen 80;
# listen [::]:80;
#
# server_name example.com;
#
# root /var/www/example.com;
# index index.html;
#
# location / {
# try_files $uri $uri/ =404;
# }
#}