Navigation

    • Register
    • Login
    • Search
    • Recent
    • Users
    • Groups
    1. Home
    2. vfeinbox
    V
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 8
    • Best 0
    • Groups 0

    vfeinbox

    @vfeinbox

    0
    Reputation
    1
    Profile views
    8
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    vfeinbox Follow

    Latest posts made by vfeinbox

    • RE: Starting vesta-nginx: nginx: [emerg] unknown directive "pagespeed" in /usr/local/vesta/nginx/conf/nginx.conf:102

      I added the "pagespeed on content" to nginx.conf file weeks ago (and vesta was not down at that time).

      I was just following the tutorial at
      https://www.mysterydata.com/how-to-install-ngx_pagespeed-with-nginx-cwp-vestacp-and-on-linux-os/

      posted in HestiaCP/VestaCP
      V
      vfeinbox
    • RE: Starting vesta-nginx: nginx: [emerg] unknown directive "pagespeed" in /usr/local/vesta/nginx/conf/nginx.conf:102

      Hi Sandeep,

      I pasted here the content of nginx.conf here... However, note that there was a time in which the pagespeed content was in that file and, in spite of that, the vesta was loading OK.

      Today, AFTER I removed the pagespeed content from nginx.conf, the vesta panel became loading/working OK again.

      However, my sites are still not loading, except one of them as I mentioned above. They show me either ERR_CONNECTION_CLOSED (the one with vesta SSL) or Error 525 SSL handshake failed (for those on Cloudfare SSL)

      Thank you

      posted in HestiaCP/VestaCP
      V
      vfeinbox
    • RE: Starting vesta-nginx: nginx: [emerg] unknown directive "pagespeed" in /usr/local/vesta/nginx/conf/nginx.conf:102

      user admin;
      worker_processes 1;
      error_log /usr/local/vesta/log/nginx-error.log;
      pid /var/run/vesta-nginx.pid;

      events {
      worker_connections 128;
      use epoll;
      }

      http {
      # Main settings
      sendfile on;
      tcp_nopush on;
      tcp_nodelay on;
      client_header_timeout 1m;
      client_body_timeout 3m;
      client_header_buffer_size 2k;
      client_body_buffer_size 256k;
      client_max_body_size 256m;
      large_client_header_buffers 4 8k;
      send_timeout 30;
      keepalive_timeout 60 60;
      reset_timedout_connection on;
      server_tokens off;
      server_name_in_redirect off;
      server_names_hash_max_size 512;
      server_names_hash_bucket_size 512;

      # Log format
      log_format  main    '$remote_addr - $remote_user [$time_local] $request '
                          '"$status" $body_bytes_sent "$http_referer" '
                          '"$http_user_agent" "$http_x_forwarded_for"';
      log_format  bytes   '$body_bytes_sent';
      access_log          /usr/local/vesta/log/nginx-access.log main;
      
      # SSL PCI Compliance
      ssl_protocols               TLSv1.2 TLSv1.1 TLSv1;
      ssl_ciphers                 EECDH+AES128:RSA+AES128:EECDH+AES256:RSA+AES256:EECDH+3DES:RSA+3DES:!MD5;
      ssl_session_cache           shared:SSL:10m;
      ssl_prefer_server_ciphers   on;
      
      # Mime settings
      include             /usr/local/vesta/nginx/conf/mime.types;
      default_type        application/octet-stream;
      
      # Compression
      gzip                on;
      gzip_comp_level     9;
      gzip_min_length     512;
      gzip_buffers        8 64k;
      gzip_types          text/plain text/css text/javascript
                          application/x-javascript application/javascript;
      gzip_proxied        any;
      
      # Proxy settings
      proxy_redirect      off;
      proxy_set_header    Host            $host;
      proxy_set_header    X-Real-IP       $remote_addr;
      proxy_set_header    X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_pass_header   Set-Cookie;
      proxy_connect_timeout   90;
      proxy_send_timeout  90;
      proxy_read_timeout  90;
      proxy_buffers       32 4k;
      fastcgi_read_timeout 300;
      
      # Error pages
      error_page          403          /error/403.html;
      error_page          404          /error/404.html;
      error_page          502 503 504  /error/50x.html;
      
      # Vhost
      server {
          listen          8083;
          server_name      _;
          root            /usr/local/vesta/web;
          charset          utf-8;
      
          # Fix error "The plain HTTP request was sent to HTTPS port"
          error_page      497 https://$host:$server_port$request_uri;
      
          ssl                  on;
         
          ssl_certificate      /usr/local/vesta/ssl/certificate.crt;
          ssl_certificate_key  /usr/local/vesta/ssl/certificate.key;
          ssl_session_cache    shared:SSL:10m;
          ssl_session_timeout  10m;
      
          error_page      404     /error/404/index.html;
          error_page      403     /error/index.html;
          error_page      500     /error/index.html;
      
          # Pagespeed
          pagespeed on;
          pagespeed FileCachePath /var/ngx_pagespeed_cache;
          location ~ "\.pagespeed\.([a-z]\.)?[a-z]{2}\.[^.]{10}\.[^.]+" { add_header "" ""; }
          location ~ "^/ngx_pagespeed_static/" { }
          location ~ "^/ngx_pagespeed_beacon" { }
      
          location / {
              expires max;
      
              index   index.php;
          }
      
          location /error/ {
              expires max;
              index   index.html;
          }
      
          location /rrd/ {
              expires off;
              internal;
          }
      
          location /backup/ {
              root    /;
              internal;
          }
      
          location ~ \.php$ {
              include         /usr/local/vesta/nginx/conf/fastcgi_params;
              fastcgi_param   SCRIPT_FILENAME /usr/local/vesta/web/$fastcgi_script_name;
              fastcgi_param   QUERY_STRING    $query_string;
              fastcgi_pass    unix:/var/run/vesta-php.sock;
              fastcgi_intercept_errors        on;
              break;
          }
      }
      

      }

      posted in HestiaCP/VestaCP
      V
      vfeinbox
    • Starting vesta-nginx: nginx: [emerg] unknown directive "pagespeed" in /usr/local/vesta/nginx/conf/nginx.conf:102

      Hey folks,

      THE ISSUE NOW:
      -- The vesta panel failed to load

      • Site A = It is working properly if I type domain.com (But if I type www.domain.com, it simply does not load) . This site has no SSL

      • Site B = It does not load anyway. This site has a cloudflare SSL and show me a 525 error: SSL handshake failed

      • Site C = It does not load anyway. This site has a vesta SSL and show me an ERR_CONNECTION_CLOSED

      • The command systemctl status vesta shows me
        Nov 12 15:08:58 panel.asheus.com vesta[70179]: Starting vesta-nginx: nginx: [emerg] unknown directive "pagespeed" in /usr/local/vesta/nginx/conf/nginx.conf:102
        Nov 12 15:08:58 mydomain.com vesta[70179]: [FAILED]
        Nov 12 15:08:58 mydomain.com systemd[1]: vesta.service: control process exited, code=exited status=1
        Nov 12 15:08:58 mydomain.com systemd[1]: Failed to start SYSV: Run vesta web server.
        Nov 12 15:08:58 mydomain.com systemd[1]: Unit vesta.service entered failed state.
        Nov 12 15:08:58 mydomain.com systemd[1]: vesta.service failed.

      • I checked that the line 102 corresponds to pagespeed on;

      • The command /var/log/nginx-error.log shows me
        2020/10/31 00:42:22 [error] 2103#0: *11622 open() "/usr/local/vesta/web/list/csf/lfd_year.gif" failed (13: Permission denied), client: 200.152.99.169, server: _, request: "GET /list/csf/lfd_year.gif?text=1604104941 HTTP/1.1", host: "panel.asheus.com:8083", referrer: "https://panel.asheus.com:8083/list/csf/frame.php"

      • The command vim /var/log/messages shows me
        kcguT-000Hfb-Uw Tainted filename '/etc/exim/domains/mydomain.com/dkim.pem'
        kcguT-000Hfb-Uw unable to open file for reading: /etc/exim/domains/ mydomain.com/dkim.pem

      The vesta panel and all sites were working well on Centos 7. The last thing I did was tapping on CSF firewall GUI. Then, suddenly, my vesta panel was down and it has no loaded anymore. Only the database, ngnix, csf firewall, http://myIP/webmail/ and http://myIP/phpmyadmin/ are ALL working well.

      Please, advise me. I am newbie. Thank you!
      PS: Via SSH, I restored a backup that I downloaded to my PC when vesta was OK, but the problem did not disappear.

      posted in HestiaCP/VestaCP
      V
      vfeinbox
    • RE: Vesta login page not loading + DNS_PROBE_FINISHED_NXDOMAIN

      Hey sandeep,

      My Vesta is active and running (the service is running).

      My Vesta panel (i.e. the Vesta admim login page) is not loading

      Thx

      posted in CWP - Panel
      V
      vfeinbox
    • RE: Vesta login page not loading + DNS_PROBE_FINISHED_NXDOMAIN

      nginx-access-log.png

      Today I opened the ngnix-access.log file and see that my server was actually hacked.

      The Vestacp panel and my sites were not loading between 27 and 28/September, which aligns to the days of the attacks in yellow.

      I am newbie to Linux, so I would be grateful if anyone could teach me to restore my Vesta panel.

      Now, I am trying to learn a good example of installantion of Fail2Ban in Centos 7 and how to set up an advanced conofiguration for it. Anyone knows one?

      Thx

      posted in CWP - Panel
      V
      vfeinbox
    • RE: Vesta login page not loading + DNS_PROBE_FINISHED_NXDOMAIN

      error 1.png

      This is the error message I am receiving when I type the URL of my sites or the URL of Vestacp login page

      posted in CWP - Panel
      V
      vfeinbox
    • Vesta login page not loading + DNS_PROBE_FINISHED_NXDOMAIN

      Hey guys,

      A few days ago, the error DNS_PROBE_FINISHED_NXDOMAIN was appearing to all my sites as well in the vesta login page. I cleanned the Google cache, typed "service vesta restart" / "systemctl restart vesta
      " on terminal, and finally I tried all the 8 steps suggested by the following Hostinger post (https://www.hostinger.com/tutorials/fix-dns_probe_finished_nxdomain), but the issue persists.

      Through SSH, I saw that my vesta service, nginx, and databases are all active. Then, I took a site that was not loading (i.e. showing the DNS error) and added today to cloudflare, so this particular site loaded normally (It means that my database is ok)

      However, I wish to be able to login through Vesta panel and use the File Manager. Could you please give me some advice?

      Thx

      posted in CWP - Panel
      V
      vfeinbox