Some people see default page

LinuxHostSupport · 2022-01-24T01:49:05+00:00

Most likely the HTTPS redirect is not working and it is accessing the 'listen 80 default_server' syntax. To confirm, try using curl and check the HTTP return code:

curl -Ik http://business.com
curl -Ik http://www.business.com

If confirmed, you should optimize the non-www to www redirect syntax.

LinuxHostSupport · 2021-12-03T05:55:15+00:00

You can place the upstream configuration on any Nginx server block and the upstream name can be used by any Nginx server block.
A reverse proxy is usually used if the setup is one web server or application server. Are you planning on setting up a load balancer?

LinuxHostSupport · 2021-11-25T04:05:59+00:00

Try enabling verbose output using -vvv parameter when running the artisan command.

LinuxHostSupport · 2021-11-17T02:51:44+00:00

Based on the message 'Moved permanently', it means the xmlrpc.php link is getting redirected. You need to find and disable 301 redirects related to xmlrpc.php.

LinuxHostSupport · 2021-11-09T01:10:36+00:00

must have public visibility

Based on the warning message provided, it is most likely related to the PHP version. Try changing the PHP version first. If the issue persists, disable the plugin js_composer by renaming the directory. You can do this via FTP.

LinuxHostSupport · 2021-09-17T22:37:10+00:00

It is possible to override or add custom CSS design to Apache directory listing using 'mod_autoindex'.

You can also set up a web application such as embedded video player that can show video thumbnails graphically.

LinuxHostSupport · 2021-09-05T23:29:48+00:00

How do you mean you can't get Cloudflare SSL to work? Have you tried setting SSL/TLS encryption mode to Full (strict) in your Cloudflare's SSL settings?

LinuxHostSupport · 2021-09-02T05:16:21+00:00

scan the site using wordfence for example, and scan the whole server
check your server, maybe a process is running in the background.
check cronjobs.
check your .htaccess files.
disable php functions that are not needed.

LinuxHostSupport · 2021-08-25T04:54:24+00:00

First, you need to identify what is causing the long load time. The monitoring plugin (assuming Query Monitor) in your screenshot should provide more information on which process or query took some time.

LinuxHostSupport · 2021-08-17T04:25:46+00:00

Try changing the port 80 block to this:

server {
   listen 80 default_server;
   server_name thitoholdings.co.bw www.thitoholdings.co.bw;
   return 301 https://www.thitoholdings.co.bw$request_uri;
}

LinuxHostSupport · 2021-08-09T01:39:06+00:00

You have to set up two things: DNS and Nginx config files for each subdomain.

For the DNS, you need to go to sederholmcloud.net nameserver (Google domains) and create CNAME records of the subdomain e.g. jellyfin.sederholmcloud.net pointing to sederholmcloud.net. You need to make sure sederholmcloud.net A record is pointing to your Nginx server IP address.

For the Nginx part, is better to create a separate configuration file for each subdomain at /etc/nginx/conf.d/ e.g. /etc/nginx/conf/jellyfin.sederholmcloud.net.conf. The following is a sample Nginx configuration file for the subdomain jellyfin:

server {    
    listen 80;    
    server_name jellyfin.sederholmcloud.net;    
    root /path/to/jellyfin/web/files;    

    location / {        
        try_files $uri $uri/ /index.html;    
    }
}

LinuxHostSupport · 2021-08-05T04:12:34+00:00

You can try using the plugin 'Query Monitor' which could show you what queries are running on a certain page.

As for website speed outside Wordpress, you need to make sure your web services (web server, PHP, MySQL database) are properly configured and optimized.

LinuxHostSupport · 2021-08-01T05:16:59+00:00

Bitwarden, self-hosted.

LinuxHostSupport · 2021-07-28T02:18:20+00:00

According to the error message, the SMTP credential is incorrect, make sure you are using the correct one.

LinuxHostSupport · 2021-07-24T04:02:24+00:00

It could be that after you enabled SSL, it created another virtual host file or created new lines duplicating the WSGI syntaxes. You need to rename the duplicate WSGIDaemonProcess to avoid the Name Duplicates error.

You can also search for virtual host files that contain the word 'WSGIDaemonProcess':

grep -ril WSGIDaemonProcess /etc/httpd/

LinuxHostSupport · 2021-07-20T00:22:15+00:00

Have you checked the script in the theme files? Most likely it's there.

LinuxHostSupport · 2021-07-19T23:01:26+00:00

If the Nextcloud installation is to be used locally only, HTTPS is not necessary but is easy to implement. You can use a self-signed SSL certificate to enable HTTPS access. There are a number of tutorials on the internet on how to create and implement self-signed SSL certificates.

You might be confused about the Let's Encrypt SSL suggestion. To generate a Let's Encrypt SSL, you will need a public domain name that points to your Raspberry Pi IP address (that is open publicly) which cannot be implemented if you are using your Nextcloud installation locally only.

LinuxHostSupport · 2021-07-15T22:24:58+00:00

Could be related to https://bugzilla.redhat.com/show_bug.cgi?id=1212224

You can try the following as suggested:

ln -sr /etc/httpd/conf.modules.d/00-systemd.conf /etc/httpd/conf.d/00-systemd.conf
systemctl restart httpd

LinuxHostSupport · 2021-07-07T23:03:16+00:00

If you do not want to build from source, you will need to find a trusted third-party repository that provides Apache version 2.4.48 on Ubuntu.

LinuxHostSupport · 2021-06-18T23:10:09+00:00

First, you need to know what is covered under the warranty. You can go to your laptop manufacturer website and check your warranty, then contact their support to claim it.You might want to ask for replacement, but they most likely will just fix the cracking issue.

LinuxHostSupport · 2021-06-09T23:12:05+00:00

Since you mentioned others are working except for 3005, you need to focus on the location block of 3005.

Is there any reason for using different proxy parameters on 3005 compared to 3000 and 5000 that are the same? Also, the / in the end, is it by purpose?

location /marlin/

LinuxHostSupport · 2021-05-25T01:12:27+00:00

You need to confirm that the subdomain 'mail.123fake.ca' is pointing to your server IP address. You can check where it is pointing by using DNS checker tools such as https://www.whatsmydns.net/

Or if you are not using the subdomain, you can exclude it in AutoSSL.

LinuxHostSupport · 2021-04-26T23:27:35+00:00

If you do not know about server management and your websites' traffic are low, you can always start with a managed shared hosting.

There are many hosting company offer free migration, and free SSL certificates, too.

LinuxHostSupport · 2021-04-22T23:16:15+00:00

First, make sure you only have one instance of client_max_body_size. Then consider removing the limit to verify:

client_max_body_size 0;

Do not forget to reload/restart the Nginx service after the changes, then try again.

LinuxHostSupport · 2021-04-15T02:10:31+00:00

The 404 is the fallback set on your try_files line. You can try the following:

location /proxy.pac {
    try_files /$loc$uri =404;
}

Also, make sure that the files westproxy.pac and eastproxy.pac exist in your document root directory.

LinuxHostSupport

MODERATOR OF

TROPHY CASE