Name Hero

Do you have a valid SSL certificate installed on your website?

Since you didn’t post the URL I can’t check, but you can use this tool:

https://www.sslshopper.com/ssl-checker.html

Simply enter in the URL of your website and make sure there is a valid and trusted SSL certificate installed.

If not, check with your web host to see if they offer them. Nowadays most web hosts have Let’s Encrypt which is free and automatic for domains.

@webmarketingctm You’re most welcome :). Glad you were able to get it resolved!

These tables will be created during installation.

Are you following these steps here?

Are either of your servers running a firewall such as iptables?

If so, you may want to try whitelisting each server to accept incoming and outgoing connections:

SSH Into 11.111.11.11:

# iptables -A INPUT -s 22.22.22.22 -j ACCEPT

# iptables -A OUTPUT -s 22.22.22.22 -j ACCEPT

SSH Into 22.22.22.22:

# iptables -A INPUT -s 11.111.11.11 -j ACCEPT

# iptables -A OUTPUT -s 11.111.11.11 -j ACCEPT

For the heck of it, you may also wish to check and make sure your wp-config.php file is using the correct table prefix as this can sometimes get overlooked ;).

Good luck!

Without knowing the specifics behind your hosting environment I have to make some assumptions to answer your questions.

At the moment I am using the IP address/subfolder (12.34.56.78/folder for example) to contain the site files. When it comes to switching the 3rd party domain name to point to the new hosting provider, is it as simple as just changing the site URL’s in the general settings on the WordPress dashboard?

Yes, you’d want to modify the General Settings to reflect the actual URL of the website. Personally, I like to do this through PHPMyAdmin modifying the Options table.

I’m assuming that the /folder lives right below the public_html folder (i.e. /home/user/public_html/folder). If that’s the case, I’d recommend moving these files up a level to be inside the public_html folder.

If you’re using a FTP program, you could select all the files in the sub folder, and drop them in the appropriate directory.

If you’re using SSH, you can simply run:

mv folder/* .

Also will I need to add a CNAME or an A name with the 3rd party domain provider as I am pointing to a ‘/subfolder’. At the moment if I just type in the Web address without the ‘/folder’ bit, I get a blank white page.

Apache actually controls all of this for you. That’s why I recommend moving the files inside the public_html directory (or the directory configured in Apache for your public-facing files).

Once the files are in the right place, you should be all set to point the domain to the IP address, given the proper DNS entries are in place.

domain.com IN A 12.34.56.78

If you didn’t build/configure the hosting environment, you may want to get with the web host, or the person that did first, to make sure you’re moving things to the proper directories :).

Good luck!

It looks like your website is no longer online, but I do see an error_log file which likely contains the details behind the 500 error.

FTP into your website or use cPanel -> File Manager to view that file and it should tell you what needs to be done.

If you’re not familiar with PHP errors, feel free to post the contents in here and I’ll give you my suggestions.

Allowed memory size of 67108864 bytes exhausted indicates your memory limit for PHP is set less than 67MB.

Nowadays, with WordPress, I recommend this setting being at least 128MB as many of the most popular themes now require this.

Before you work on increasing it, it’s always good to find out what your PHP memory limit currently is.

To do this, create a new file in your root WordPress installation called “info.php.” Inside that file, put the following contents:

<?php

// Show all information, defaults to INFO_ALL
phpinfo();

?>

Visit the file in your web browser and search for:

memory_limit

This value will tell you what your current hosting environment is set to.

You could then use the suggestions the poster above me recommended to try and increase it. Once you do so, reference that info.php file to see if the changes applied correctly.

A lot of web hosts allow you to control this value by creating a php.ini file in the directory right above your public_html or inside of cPanel (using the PHP Selector).

If all else fails though, raise the issue with your web host, and tell them you need your PHP memory limit set to at least 128MB. They should know exactly what to do as this is very common amongst the WordPress community.

Good luck!

This error can also be corrected by increasing your PHP Memory Limit.

Allowed memory size of 41943040 bytes exhausted – Indicated your PHP Memory limit is set to lower than 41 MB.

A lot of themes nowadays (such as Divi) require a memory limit of at least 128MB.

To see exactly what your PHP Memory Limit is:

* Create a new file in the root folder of your WordPress installation called info.php

* Place the following code inside:

<?php

// Show all information, defaults to INFO_ALL
phpinfo();

?>

* Access the file from your web browser (i.e. https://yourdomain.com/wordpress/info.php

* Look for memory_limit

Depending on what value this is, I would recommend increasing to at least 128MB to avoid such errors with future plugins/themes.

A lot of web hosts allow you to modify this limit from inside of cPanel or with a custom php.ini file inside your /path/to/home.

Good luck!

A 3MB Upload limit is really low.

Check out this article in their knowledgebase that will show you how to increase this via a custom php.ini file.

Personally, I set mine to at least 32MB as sometimes I have some really large media files that I don’t want to have to compress inside of Photoshop.

Instead, I use ShortPixel Image Optimizer which will automatically compress and optimize on upload.

It’s free for your first 100 images, then credits are pretty cheap. I went ahead and bought some as it really increased the loadtime of my blog.

Hope this gets you straightened out! Good luck!

It’s loading really slow here.

If I check the site using Google Chrome’s developer Console, I see a couple concerning errors:

Failed to load resource: the server responded with a status of 500 (Internal Server Error)
jquery-migrate.min.js?ver=1.4.1:2 JQMIGRATE: Migrate is installed, version 1.4.1
custom_admin.php Failed to load resource: the server responded with a status of 500 (Internal Server Error)
(index):565 GET https://www.kameleonchic.com/%E2%80%9C/s7.addthis.com/js/300/addthis_widget.js 404 (Not Found)

The 500 Internal Server Errors are coming from this URL:

https://www.kameleonchic.com/wp-content/plugins/wp-stats-manager/css/custom_admin.php?ver=1.0.0

I would recommend disabling the Wp Stats Manager plugin and then seeing if the site responds faster.

If so, I would then recommend re-installing or upgrading the plugin so you can get rid of that 500 Internal Server Error.

That should solve your issue!

Good luck!

If your friend has access to cPanel you may want to login to File Manager from there, click the cog on the top to view hidden files, and then look.

You may also want to try another FTP program for the heck of it.

If you’re using a Mac I like Transmit but there is also Filezilla.

Also, if you have SSH access you can navigate to the /wp-admin folder:

cd /path/to/wp-admin

and then type:

ls -l

To see if the .htaccess file is there.

Finally, if he is using cPanel, you may want to go to “Directory Privacy” to see if it’s inside of there.

If all else fails, perhaps reach out to his web host to make sure they haven’t added a global .htaccess for the wp-admin directory. This is a common practice if they’ve recently had a brute-force attack on the server.

Good luck!

Looks like they’ve completely suspended the website as I just get their default suspended page when I try to access your website.

I would personally recommend giving them a call (or live chat) and asking them what specific limit you’ve reached. For example, disk space, Inode limit, CPU usage, mySQL connections, etc.

Once you know this, you can then evaluate your best option to getting the website back online. If you’re wanting to stay with BlueHost, they may have an upgrade to the package your on or maybe able to move you over to a VPS.

Good luck!

Personally, I wouldn’t recommend emailing that many subscribes inside of WordPress.

If you’re on a shared hosting plan, your web host may even suspend you if they suspect you’re spamming. They also may have really low email relay limits making this task impossible.

If you’re on a VPS or dedicated server, you’ll have better luck, but you’re also going to be fighting against actually inboxing your users.

Whenever I want to do a mass mailing such as this, I use https://convertkit.com/ (there are many others out there) where you can export your users from WordPress, import them into the email provider, and then email them this way.

Using tools such as this, you can track the mailing every step of the way, and will also have a much higher inboxing rate. Just make sure everything you’re doing is CAN-SPAM compliant :).

Good luck!

Looks like the domain has been placed on hold at the registrar level:

Domain Status: clientHold https://icann.org/epp#clientHold

https://whois.domaintools.com/swaytheory.com

ICANN requires all domains to use a valid email address in their Whois data.

If you ever updated this, it’s likely your domain registrar sent you a verification email to your contact address on file.

You have to click that link inside for the domain to stay active.

I’d recommend checking your Spam folder for your Registrant Email (I won’t publish it here) and looking for that verification email.

If you don’t see it, reach out to your domain registrar and have them re-send the verification email.

Once you click that verification link, your website will come back within a few hours.

I’ve seen this problem before.

The fix for me was to SSH into my website and run the following:

chown USERNAME.USERNAME FILE.pdf

This assigned my “web user” access to the file, which allowed it to be downloaded via web browser. In my case, the permissions were lose when I migrated over from another server.

Also, you may want to try setting the permissions to 644 vs. 604.

Good luck!