The 500 Internal Server Error can be very frustrating because it is such a vague error. In addition to the error message being vague, there are actually several issues that can cause the 500 error message to appear.

What causes 500 Internal Server Errors?

Here are the three most common reasons:

  1. File permissons set incorrectly. Most commonly having a file as "world" writeable. This is a very common issue with PHP files. In general on our servers, PHP file permissions should not be higher than 775. Keep in mind too that the permissions of the parent folders/directories need to be set correctly too. See our File Permissons article for more information, including how to change those permissions.

  2. Leaving file permissions set incorrectly after manual installation of content management systems, forums, blogs, etc.

  3. Coding errors in the .htaccess file.

Correcting a 500 Server Error:

To track down what is causing the error, you will want to start with the error log in cPanel. Once you are logged into your cPanel look for and click on the "Error Log" icon under "Logs."


For example, if I set a PHP file to 777 permisions (writeable by the world) this will cause a 500 Internal Server Error. I would be able to view something similar to the following in my Error Log:

[Tue Sep 20 08:18:01 2011] [error] [client] SoftException in Application.cpp:264: File "/home/username/public_html/concrete/index.php" is writeable by others

I would correct this by changing the permissions of the index.php file to 644.

Perl Scripts and 500 Errors

While a 500 error from a Perl script error may not be common, it can be even harder to track down because the cPanel Error Log does not tell us in this case what specifically caused the 500 error message. You will want to track down the code causing the error. It can even be something as simple as one missing character in your code. For instance, in the following code:

print "content-type: text/html \n\n"
print "Hello, PERL!";

The second line is missing a semi-colon at the end, so:

print "content-type: text/html \n\n"


print "content-type: text/html \n\n";

There are many different possible causes of 500 errors, so it is difficult to give an example of each and every situation. If you've looked for the above causes but are unsure on what needs to be done next to fix the problem, please contact technical support. We're available 24/7 and we're always happy to help.

Did you find this article helpful?

We value your feedback!

Why was this article not helpful? (Check all that apply)
The article is too difficult or too technical to follow.
There is a step or detail missing from the instructions.
The information is incorrect or out-of-date.
It does not resolve the question/problem I have.
How did you find this article?
Please tell us how we can improve this article:
Email Address

new! - Enter your name and email address above and we will post your feedback in the comments on this page!

Like this Article?

Related Questions

Here are a few questions related to this article that our customers have asked:
Ooops! It looks like there are no questions about this page.
Would you like to ask a question about this page? If so, click the button below!
Ask a Question
n/a Points
2014-04-16 3:34 pm

500 Internal Server Error - I can't fix it.

9,962 Points
2014-04-16 4:27 pm
Hello Luis,

We'd need a bit more information in order to assist with your issues. It looks like currently your're running a PrestaShop website in maintenance mode. Did you do anything to your store prior to the 500 Internal Server Errors happening?

- Jacob
n/a Points
2014-05-05 9:30 am

Hi,     I am trying to get a single page site up and running using a theme I purchased, but it is failing to load nearly all image assets, I am getting 500 errors in the console and network tabs of my browsers.I have gone through and checked the permissions of the relevant files (755) and folders (644) but haven't found any indication why this would happen. Most of these images are static referenced from a html page.The url is weird thing is if I work out the direct URL of the image, I can navigate to that successfully, this issue is weirding me out!Also, I can't see anything in the logs in CPanel...Any help is much appreciated.

17,014 Points
2014-05-05 12:20 pm
Hello Chris,
In investigating your issue I discovered two actual problems. The reason the images were not showing for the domain is because of the .htaccess hotlink prevention code in your primary domain name. .htaccess files are recursive so the rules apply to all folders underneath them. The code was also restricting things in the addon domain since they were not from the primary domain name. I was able to correct that in a test .htaccess file.

The second issue was that the default image you wanted to display for hotlinking was not showing up. This is why you were unable to see that this was the cause. The hotlink protection code points to an image that is also hotlink protected. This sends the server into an endless loop and will not display anything. After fixing this issue, the addon domain displayed the default image all over it. The image you want to display has to be external to the site to prevent the looping. For the test, I called an image from imgur that says Do Not Hotlink. This works well.

Both issues were simply the result of the htaccess code for hotlinking not performing as it should. The original code is below. ( is used in place of your primary domain name for privacy).

RewriteCond %{HTTP_REFERER} !^http://(.+\.)?example\.com/ [NC]
RewriteCond %{HTTP_REFERER} !^$
RewriteRule .*\.(jpg|gif|bmp|png)$ /images/dontsteal.jpg [L]

While not perfect, the code below is what I ended up with. ( is used in place of your primary domain name for privacy).

RewriteCond %{HTTP_HOST} ^$ [OR]
RewriteCond %{HTTP_HOST}$
RewriteCond %{HTTP_REFERER} !^$
RewriteRule .*\.(jpe?g|gif|bmp|png)$ [L]

I saved your original .htaccess file as .htaccess.original to preserve your original code so you can see and left the modified .htaccess file in place. Both the addon domain and the hotlinking warnign image are now working. Feel free to replace the imgur-linked image with one of your own, but remember to not store it in the hotlink protected domain.

Kindest Regards,
Scott M
n/a Points
2014-06-13 9:43 am


My site has been showing an internal server error since this morning but there are no errors in my error log.  What further steps can I take to try to identify the problem and resolve it?

Thank you


8,065 Points
2014-06-13 9:57 am
This is typically caused by an issue within your .htaccess file. I recommend using the cPanel File Manager to open your .htaccess file and take a look at it.
n/a Points
2014-06-13 10:38 am

Hi Jeff, thank you for the quick reply.  I've got the file open and am comparing it to a generic WordPress file but I'm afraid I don't see anything wrong.  Do you have any other suggestions?    

8,065 Points
2014-06-13 10:41 am
Try renaming any .htaccess files that are within your home directory, public_html directory, or any others that may be hiding in there.
n/a Points
2014-06-13 10:47 am

Ok!  I'm a total beginner at this so just to check: what should I be renaming them to?  .ht anything?  Thank you for being so quick with your replies, I really appreciate it!

8,065 Points
2014-06-13 11:03 am
Anything other than .htaccess is perfectly fine. Personally, I name them .htaccess.old.
n/a Points
2014-06-13 11:09 am

Thanks!  I've done a search for all .htaccess files (only two) and have renamed them as you suggested.  Now a new .htaccess file has appeared but it's empty.  Am I supposed to do something with that file?  I still get the 500 internal server error on the site.

8,065 Points
2014-06-13 11:13 am
Empty .htaccess files are fine. Are you hosted with us? Could you provide me with the domain for the site that you are having issues with?
n/a Points
2014-06-13 11:17 am

Yes I'm hosted by you guys :)  The domain is

16,176 Points
2014-06-13 11:47 am
Hello Sophie,

Sorry for the problem! I was able to find the issue as a problem with the php.ini file. We have a default one that is running directly from the server. I set it to use that one and the site works okay now. The php.ini on your site was referencing an older function. I simply renamed it so that the server php.ini would take precedence and then the site worked fine.

Let us know if you have any further issues!

Kindest regards,
Arnel C.
n/a Points
2014-06-13 11:51 am

Thank you thank you!  There's no way I would have figured that out!

n/a Points
2014-06-13 12:08 pm

I'm back!  The site is back up now but I now get a 404 error on my comments pages.  How do I fix this?  Does this still have to do with the php.ini file?

'The document you are looking for may have been removed or re-named. Please contact the web site owner for further assistance.'


16,176 Points
2014-06-13 12:31 pm
Hi Sophie,

Sorry for that problem! If you recently imported a WordPress site from another location, one of the things that needs to be reset is the permalinks. This can be found in your Admin dashboard under Settings (you can also reference our article Setting up Permalinks if needed).

To reset your permalinks you make a copy of our custom permalinks from before, then click on DEFAULT in the permalinks structure and save. This will make the links that ugly number-code string that it uses by default. After it's saved, simply paste your custom permalinks back in and save. This will rebuild the links in the database with the correct path.

I've done this for you already - as it's a pretty quick fix, but I just wanted to let you know how that works. Let me know if you're still seeing a problem with the pages. If you are, make sure to first clear your browser cache. This will make sure that your browser isn't using the old paths.

Hope that helps! Please let us know if you have any further issues!

Arnel C.
n/a Points
2014-06-14 3:46 am


euhm.. what do i do if i Need to set a folder CHMOD to 777 for something? for example i've been trying to use some PHP scripts for showing news via MYSQL on my web, but it won't work if i don't set the perms to 777, somehow the "log in" from the news Admin panel brings me back to the "log in" page even if i enter the correct user and password, given in the instructions of the PHP script...

so i'm trapped between the 500 error and the requeriments of the PHP script

ty very much in advance. PS. if you know a good (free) PHP script that shows notices on your page and lets you modify them WYSIWYG and that works without the need of CHMODing to 777, i'd thank you Very much!

8,065 Points
2014-06-16 8:47 am
Setting scripts and folders to 777 is extremely dangerous. So dangerous, in fact, that setting these permissions opens your site to becoming hacked within seconds. If your script requires you to set permissions to 777, I highly recommend finding another script as this one would be very poorly coded and greatly opens you up to attack.
n/a Points
2014-06-21 12:04 pm

Hi Guys,

Just FYI, I had the same issue that Sophie was dealing with. I removed the php.ini file from my home directory and the site worked again. 

I'm assuming there's lots of other people out there that may be experiencing the same issue. Thank you for making the fix public. It saved me a lot of time.


n/a Points
2014-06-24 1:20 pm

I'm trying to set up security with php and mysqli for a small database. Opening the login page throws the 500 Internal Server error. The error log shows File does not exist: /home/.../public_html/500.shtml. 


I start the login.php page:





include_once 'php/db_connect.php';

include_once 'php/functions.php';




if (login_check($mysqli) == true) {

    $logged = 'in';

} else {

    $logged = 'out';




The functions.php page starts with this function:




include_once 'php/psl-config.php';


function sec_session_start() {

    $session_name = 'sec_session_id';   // Set a custom session name 

    $secure = 'SECURE';


    // This stops JavaScript being able to access the session id.

    $httponly = true;


    // Forces sessions to only use cookies.

    if (!ini_set('session.use_only_cookies', 1)) {

        header("php/error.php?err=Could not initiate a safe session (ini_set)");




    // Gets current cookies params.

    $cookieParams = session_get_cookie_params();

    session_set_cookie_params($cookieParams["lifetime"], $cookieParams["path"], $cookieParams["domain"], $secure, $httponly);


    // Sets the session name to the one set above.



    session_start();            // Start the PHP session 

    session_regenerate_id();    // regenerated the session, delete the old one. 



and the db_connect.php only has




include_once 'php/psl-config.php';   // Needed because functions.php is not included


$mysqli = new mysqli(HOST, USER, PASSWORD, DATABASE);

if ($mysqli->connect_error) {

    header("php/error.php?err=Unable to connect to MySQL");




the psl-config.php page just defines the database parameters



 * These are the database login details


define("HOST", "localhost");     // The host you want to connect to.

define("USER", "me");    // The database username. 

define("PASSWORD", "*****");    // The database password. 

define("DATABASE", "mydatabase");    // The database name.


Any idea what the issue is?

16,176 Points
2014-06-24 1:49 pm
Hello Gene,

Thanks for the question. Since we have no way of seeing the files or error logs for your site (without any account information or access), then we're only guessing at the possible cause of the 500 error. One thing you can do is to create a PHP file that exists on your site (something simple like "hello world!"), then use it to see if your problem is in your code. You can set the reference in difference places and then see where the problem lies. Sorry we can't give you more specifics, but again, we would need to be able to access to the site files and logs to see what's happening.

Arnel C.
n/a Points
2014-06-24 2:00 pm

I think it's a path issue, but dammed if I can find it. I can give account info off line if you're inclinded to look. Otherwise I'll keep looking.

9,962 Points
2014-06-24 2:21 pm
Hello Gene,

Does your web host use cPanel? If so you should be able to click on Error Log under the Logs section to actually see the real error message. Or you should be able to contact them to review the Apache error log to see what the actual error message is.

The error you're getting now is simply stating that you're getting a 500 internal server error and that it can't locate the 500.shtml page to display the generic error.

If there is a problem with your PHP script, typically PHP will spit out a line number that is causing the problem. So you more than likely are running into a permission issue, or something at the server level attempting to be loaded by PHP such as Zend Loader or another extension is having problems.

Unfortunately really the only way to tell would be looking at the actual error message being generated on the server, and not just the front-end 500 error.

- Jacob
n/a Points
2014-06-24 2:33 pm

The cPanel error log:

[Tue Jun 24 11:23:57 2014] [error] [client File does not exist: /home/.../public_html/500.shtml

I've was getting several of these errors this morning on opening the login.php page. I cleaned them all up by fixing some of the include_once 'myfile.php' statement paths, but now I'm just getting this one error and I'm stuck. 


9,962 Points
2014-06-24 2:43 pm
Hello Gene,

Typically a server is setup to log any 500 internal server errors, but it seems like you might have an .htaccess file or your Apache config settings are set to ErrorDocument 500 500.shtml for custom error pages, so the only error the server is logging for you is that it can't find that custom error document when attempting to handle a 500 error.

Since your PHP scripts are not very long, I might recommend commenting out the entire file and then uncomment it line by line until you trigger a 500 error again to see what the culprit is. You might also want to match up the time stamp from when the 500 error was triggered in the Apache error log, with your site's access-logs to ensure the 500 error is actually being triggered by the PHP script you think is the problem.

- Jacob
n/a Points
2014-06-24 3:40 pm

I believe my issue is the path in the include_once statements


include_once 'php/db_connect.php';


include_once 'home/mediqxX/public_html/php/db_connect.php';

makes the 500 Internal Server error go away, but now I have 

Warning: include_once(home/mediqxX/public_html/php/db_connect.php) [function.include-once]: failed to open stream: No such file or directory in /home/mediqxX/public_html/login.php  on line  3

So I believe the issue is all about the path.

16,176 Points
2014-06-24 3:57 pm
Hello Gene,

It sounds like you're on the right track. The new error message also provides a more specific location. Thanks for letting us know what you've found.

Kindest regards,
Arnel C.
n/a Points
2014-06-24 4:07 pm

I can't figure out what's wrong with the path unless it has something to do with the file. I'm not versed enough to know if it is or not.

9,962 Points
2014-06-24 4:28 pm
Hello Gene,

It looks like you need to change:

include_once 'home/mediqxX/public_html/php/db_connect.php';


include_once '/home/mediqxX/public_html/php/db_connect.php';

Otherwise without the / the server is going to be interpreting the home directory as a relative instead of a full path, and won't find the db_connect.php script . However once you've included the correct file, more than likely you're going to get the generic 500 error again stating it can't find your custom 500.shtml error page.

This is because it seems like having the include set to a relative path of php/db_connect.php it was correctly finding the file so you didn't get any PHP errors, but then something in that script then triggered a 500 internal server error. Now that you've placed an incorrect path PHP is catching it and displaying that error before it triggers a server error.

You would really want to look to see why your 500 errors are not being logged and instead trying to go to a custom 500 error page. Because more than likely that is what's ultimately hiding the real problem which is more than likely a permission issue, or PHP extension or something of that nature that you're trying to use that the server doesn't have.

If you host is unable to take a look at this, we can take a look if you provide us either SSH or FTP access to the account. You can go ahead and just comment back to this post with that info and we won't make any private information public before approving your comment to be posted.

- Jacob
n/a Points
2014-06-24 4:45 pm

okay I'm here at inmotion hosting. The login is my email address for the domain

Everything I'm doing now should be around the login.php page, the donorList.php and those php pages in the php folder.

9,962 Points
2014-06-24 5:59 pm
Hello Gene,

Because you are an InMotion Hosting customer, in the future you might want to submit a ticket for this type of issue so that we know right away we have access to look around your account instead of guessing what the problem could be.

Taking a look through your files, the following files had to be updated to include the correct path for your include_once statements:


Once all of those were corrected the actual 500 error being logged in Apache was:

Zend Guard Loader requires Zend Engine API version 220090626
The Zend Engine API version 220060519 which is installed, is outdated.
malformed header from script. Bad header=error.php?err=Could not initia: login.php

It looks like your /home/userna5/.htaccess file has been set to default your account to use PHP 5.2, and your site was also loading your local /public_html/php.ini file which was causing the Zend Guard problem. We have a guide on Zend Optimizer vs Zend Guard that explains that Zend Optimizer can only be used on PHP 5.2 and older versions while Zend Guard is used in PHP 5.3 and newer, are you actively using either of these in your PHP scripts?

When I temporarily moved your php.ini file out of place to php.ini-BAK so that the server-wide one is used instead, your login.php script then triggers this error:

malformed header from script. Bad header=error.php?err=Could not initia: login.php

If I follow our guide on using multiple versions of PHP on one account and edit your /public_html/.htaccess file to default to PHP 5.3 instead with this line:

AddHandler application/x-httpd-php5 .php

Your login.php page then pulls up without any errors. But then when I attempt to login using the form on that page it then redirects me to /php/process_login.php and it's just a blank page.

I'm not sure if you needed PHP 5.2 for other aspects of your site, so I've gone ahead and left the code to activate PHP 5.3 commented out in your /public_html/.htaccess file.

Because even just a simple PHP script with phpinfo(); was still throwing a Zend error I've gone ahead and left your php.ini file as php.ini-BAK.

It sounds like if you switch your account to PHP 5.3 then you just need to work on the coding of your login form, as that seems to resolve the 500 server errors.

- Jacob
n/a Points
2014-06-25 9:22 am

Thanks for all your help Jacob. Other than these new donor/donation pages the only other php on the site is to list out two workshop schedules. I'll go through the code and upgrade the php and also change it to mySQLi as well. It had to happen sometime...LOL. This is what happens when a person learns by trial and error (once or twice a year) instead of taking formal classes.

n/a Points
2014-07-09 3:51 am

I couldn't find any records in the error log regarding to my 500 error. Also the site was working before and I haven't changed anything. It just suddenly started to show up. Could you help me with it please? Thanks!

9,962 Points
2014-07-09 4:36 am
Hello Zhe,

Sorry for the troubles, I see that you've already contacted support about this issue and they seem to have resolved the problem.

It looks like when your server recently had the default version of PHP updated to PHP 5.4 this possibly caused issues with your current scripts.

In your home directory the .htaccess file had this code placed in it:

# Use PHP53 as default
AddHandler application/x-httpd-php53 .php

This sets your account to revert back and use PHP 5.3 for PHP scripts instead.

If you encounter any other similar issues on your account, you might be interested in knowing that you can run multiple versions of PHP on one account.

Please let us know if you're still having any issues at all.

- Jacob
n/a Points
2014-08-11 3:43 pm

Hello, I am getting an internal 500 error ([Mon Aug 11 12:34:34 2014] [error] [client] File does not exist: /home/goodba7/public_html/js/jquery.js, referer:

I have been unable to trace the error, as far as I can see I have jquery.js in that folder.

This page is a form that sends the info to a php file to process, it was working, I am not sure what happened to cause this error.

Let me know if you can help,



16,176 Points
2014-08-11 4:46 pm
Hello Trevor,

I took a long look at your error and here's a portion of the Apache error log:

[Mon Aug 11 12:09:57 2014] [error] [client 7x.xx.xx.xx] PHP Warning: PHP Startup: Unable to load dynamic library '/opt/php54/lib/php/extensions/no-debug-non-zts-20100525/php_sqlite.dll' - /opt/php54/lib/php/extensions/no-debug-non-zts-20100525/php_sqlite.dll: cannot open shared object file: No such file or directory in Unknown on line 0, referer:
[Mon Aug 11 12:09:57 2014] [error] [client 7x.xx.xx.xx] PHP Warning: PHP Startup: Unable to load dynamic library '/opt/php54/lib/php/extensions/no-debug-non-zts-20100525/php_xsl.dll' - /opt/php54/lib/php/extensions/no-debug-non-zts-20100525/php_xsl.dll: cannot open shared object file: No such file or directory in Unknown on line 0, referer:
[Mon Aug 11 12:09:57 2014] [error] [client 7x.xx.xx.xx] PHP Warning: PHP Startup: Unable to load dynamic library '/opt/php54/lib/php/extensions/no-debug-non-zts-20100525/php_zip.dll' - /opt/php54/lib/php/extensions/no-debug-non-zts-20100525/php_zip.dll: cannot open shared object file: No such file or directory in Unknown on line 0, referer:
[Mon Aug 11 12:09:57 2014] [error] [client 7x.xx.xx.xx] malformed header from script. Bad header=
: window-bar-selector.php, referer:
[Mon Aug 11 12:11:05 2014] [error] [client 7x.xx.xx.xx] File does not exist: /home/goodba7/public_html/html/favicon.ico, referer:
[Mon Aug 11 12:14:57 2014] [error] [client 7x.xx.xx.xx] PHP Warning: PHP Startup: Unable to load dynamic library '/opt/php54/lib/php/extensions/no-debug-non-zts-20100525/php_gd2.dll' - /opt/php54/lib/php/extensions/no-debug-non-zts-20100525/php_gd2.dll: cannot open shared object file: No such file or directory in Unknown on line 0, referer:
[Mon Aug 11 12:14:57 2014] [error] [client 7x.xx.xx.xx] PHP Warning: PHP Startup: Unable to load dynamic library '/opt/php54/lib/php/extensions/no-debug-non-zts-20100525/php_mbstring.dll' - /opt/php54/lib/php/extensions/no-debug-non-zts-20100525/php_mbstring.dll: cannot open shared object file: No such file or directory in Unknown on line 0, referer:
[Mon Aug 11 12:14:57 2014] [error] [client 7x.xx.xx.xx] PHP Warning: PHP Startup: Unable to load dynamic library '/opt/php54/lib/php/extensions/no-debug-non-zts-20100525/php_mysql.dll' - /opt/php54/lib/php/extensions/no-debug-non-zts-20100525/php_mysql.dll: cannot open shared object file: No such file or directory in Unknown on line 0, referer:
[Mon Aug 11 12:14:57 2014] [error] [client 7x.xx.xx.xx] PHP Warning: PHP Startup: Unable to load dynamic library '/opt/php54/lib/php/extensions/no-debug-non-zts-20100525/php_pdo.dll' - /opt/php54/lib/php/extensions/no-debug-non-zts-20100525/php_pdo.dll: cannot open shared object file: No such file or directory in Unknown on line 0, referer:
[Mon Aug 11 12:14:57 2014] [error] [client 7x.xx.xx.xx] PHP Warning: PHP Startup: Unable to load dynamic library '/opt/php54/lib/php/extensions/no-debug-non-zts-20100525/php_pdo_sqlite.dll' - /opt/php54/lib/php/extensions/no-debug-non-zts-20100525/php_pdo_sqlite.dll: cannot open shared object file: No such file or directory in Unknown on line 0, referer:
[Mon Aug 11 12:14:57 2014] [error] [client 7x.xx.xx.xx] PHP Warning: PHP Startup: Unable to load dynamic library '/opt/php54/lib/php/extensions/no-debug-non-zts-20100525/php_sqlite.dll' - /opt/php54/lib/php/extensions/no-debug-non-zts-20100525/php_sqlite.dll: cannot open shared object file: No such file or directory in Unknown on line 0, referer:
[Mon Aug 11 12:14:57 2014] [error] [client 7x.xx.xx.xx] PHP Warning: PHP Startup: Unable to load dynamic library '/opt/php54/lib/php/extensions/no-debug-non-zts-20100525/php_xsl.dll' - /opt/php54/lib/php/extensions/no-debug-non-zts-20100525/php_xsl.dll: cannot open shared object file: No such file or directory in Unknown on line 0, referer:
[Mon Aug 11 12:14:57 2014] [error] [client 7x.xx.xx.xx] PHP Warning: PHP Startup: Unable to load dynamic library '/opt/php54/lib/php/extensions/no-debug-non-zts-20100525/php_zip.dll' - /opt/php54/lib/php/extensions/no-debug-non-zts-20100525/php_zip.dll: cannot open shared object file: No such file or directory in Unknown on line 0, referer:

I removed your domain name and any IP references. These errors are likely the result of an server upgrade of PHP. There are a few suggestions that may help to resolve the problem:

You can add the following to your .htaccess file (as per the post above):

# Use PHP53 as default
AddHandler application/x-httpd-php53 .php


You can also try re-naming the PHP.INI file to something like PHP.BACKUP so that it uses the server default file. I'm unable to verify exactly where you're having the problem at this point since we don't have an exact URL. Can you try using the suggestions above and then let us know if the issue is still happening? If you do continue to have the problem, please provide more information on how we can duplicate the error so that we can investigate it further.

Arnel C.
n/a Points
2014-08-13 2:08 pm

I got it working changing the php.ini file to backup.




16,176 Points
2014-08-13 2:11 pm
Good to hear, Trevor. Please let us know if you require any further assistance!

Arnel C.

Post a Comment

Email Address:
Phone Number:

Please note: Your name and comment will be displayed, but we will not show your email address.

39 Questions & Comments

Post a comment

Back to first comment | top

Need more Help?


Ask the Community!

Get help with your questions from our community of like-minded hosting users and InMotion Hosting Staff.

Current Customers

Chat: Click to Chat Now E-mail:
Call: 888-321-HOST (4678) Ticket: Submit a Support Ticket

Not a Customer?

Get web hosting from a company that is here to help. Sign up today!