This article aims to help you with upgrading your Godaddy windows Shared hosting to latest 4G hosting. We have our website code written in asp.net 3.5 with IIS 6 and faced some issues after the upgrade. We were able to resolve them after some research along with hit and trials.
Hence, I decided to write this article to help others who may also face the same issues.
How to upgrade your windows shared hosting to 4G hosting if you host multiple websites in same account?
- Log in to your Godaddy account. Go to 'Products' and then 'Web Hosting'. Click on the web hosting account name (shown in red in image). You web hosting account name could be anything. We have kept it as inHouseRecipes.com.
-
A new pop up opens up. Click on 'Edit account details' tab. Click on 'Plan' drop down box and select the '4g hosting' plan. Click save. Your hosting account would be upgraded automatically.
- If you were hosting only one website in your Godaddy windows shared hosting plan, then you are done here.
Just wait for the upgrade to complete and then test your website. It should be running fine.
But if you were hosting multiple websites in same shared windows hosting account, then you need to follow some more steps.
- Come back to the same windows hosting account page. Now click the launch button as shown in the image:
- By default, the upgrade to 4G account also upgrades your account to IIS 7 from IIS 6. Some problems occur due to the IIS change in case of multiple website hosting. hence we are trying to solve those issues. If you see that all your websites are working fine after the upgrade then you also do not need to follow further steps.
- To change the IIS settings, go to Content->IIS management:
-
Click on 'Advanced' button, then select 'classic' mode and click Ok. Now, Click on 'Recycle App' to refresh IIS 7. By default, the mode in IIS7 is set to 'Integrated'.
After the recycling, all your websites hosted in same hosting plan should work as before.
Note: In some cases, you might see that your main root website is working fine but other websites hosted in sub folders are showing up 500 internal error. You can read about
how to see the actual error instead of 500 internal error on asp.net windows hosting here. Once this error is gone, you will be able to see the actual error and then can fix it appropriately.