• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Upgrade Errors - .net no longer working

J

jjmancini

Guest
Hey Everyone!

I just upgraded from plesk 7 to plesk 7.5 and since then all of my sites containing .net or .aspx pages have given me errors and I cannot access them.

Any suggestions on how to fix this would be great. Was there a change in the way 7.5 handles .net? THanks!
 
If you will describe what kind of errors do you get then we can answer where is the problem faster. May be you've got some URL where we can take a look at that errors.
 
Well unfortunately I cannot login to any of the areas where I can view the trace files to see the error. But if you go to http://fuelstats.dukecityfueling.com then type in a ny username or password you will see the error. But it is a custom error page. So either way, since the upgrade the problems have started.

Thanks for any more suggestions!
 
I was able to fix it by just restoring the files via plesk, then I had to recreate the DB. The problem was that if databases were created outside of plesk, they were erased when the upgrade happened.

So now I have to recreate a couple more.
 
Back
Top