• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Plesk 9.2.1 Applications do not work on new domain

R

Rick Jewson

Guest
Hi,

When I install DotNetNuke 5.0.1 from the Application Vault to a pre-existing domain after upgrading from 8.2 to 9.2.1 everything works great.

If I install to a newly created domain after the 9.2.1 upgrade, the installation is successful, but when I try to access the application, I get a 404 error, even thought the files exist on the domain according to the File Manager with plesk.

I have tried deleting and reinstalling the application, but the same result.

Anyone else having this issue?
 
Hmm...
Maybe new domain is resolving somewhere else?
Also, check vhost folder where DotNetNuke is installed and try to access some existing files in browser, maybe Plesk offers incorrect path to you on SiteApps screen?
 
You must log in or register to reply here.

Similar threads

H
Resolved Unable to Disable Node.js Application in Plesk – App Remains Accessible
Replies
1
Views
910
HawkSky
H
Azurel
Question Isolating Applications in Plesk – Separation of Owner Privileges and Subdomain Management Across Subscriptions?
Replies
2
Views
340
Azurel
Azurel
M
Issue Database Connection Refused 10 mins after Deploy
Replies
1
Views
441
scsa20
scsa20
D
Resolved New domains are not working properly
Replies
3
Views
699
damack
D
Dmytro
Question Existing ImunifyAV will automatically be replaced with the new Imunify extension
Replies
6
Views
845
Manuel Jesús Gallardo
M
Back
Top