Yes, that is exactly right. I have to do that on both sites that were installed from DNN version 5.2.2 from scratch. About every 12 hours or so the site will either start timing out when it tries to reach the database, or the user sees the generic DotNetNuke error page that says "An error has ocurred" twice. When I look at the event log in the database I see this:

Object reference not set to an instance of an object. at DotNetNuke.UI.Skins.Skin.GetSkin(PageBase Page) at DotNetNuke.Framework.DefaultPage.Page_Init(Object sender, EventArgs e) at System.Web.UI.Control.OnInit ...

However, forcing the application to restart by copying a dll back to the bin folder always clears out the problem (I suppose clearing the cache) and I'm back in business again.

I agree that this is insupportable and we MUST find a resolution. I have tried changing the caching settiing but nothing seems to help.

GoDaddy says the problem is with DNN and that I should go back to version 4.9, but I can't do that without rebuilding the site from scratch and losing all my content.

I just started experiencing this problem today on the new GoDaddy server. After "resetting" the web.config file my site came back up. I am running 4.8.4 and was thinking about upgrading as soon as I had the time, but right now I'm going to wait as it appears later versions are having the same issue on this host.

It would be nice to get a little more substantial information from the support staff, instead of the usual blame the software excuse.