• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

[Bug is confirmed: EXTPLESK-3973] Path to document root is no longer generated when you add a new subdomain

Maarten

Golden Pleskian
Plesk Guru
Username:

TITLE


Path to document root is no longer generated when you add a new subdomain

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

AlmaLinux 8.6 (Sky Tiger)
Plesk Obsidian 18.0.46 Update #1

PROBLEM DESCRIPTION

When you add a new subdomain, the document root is no longer generated.
The browser console shows this error:

Code:
Uncaught TypeError: EventTarget.dispatchEvent: Argument 1 does not implement interface Event.
    handleDomainNameChange add-subdomain line 521 > injectedScript:141
    a helpers.js:74
    d try catch.js:185
    y instrument.js:458
    <anonymous> add-subdomain line 521 > injectedScript:145
    <anonymous> add-subdomain line 521 > injectedScript:144
    <anonymous> add-subdomain line 521 > injectedScript:151
    <anonymous> add-subdomain:521
    <anonymous> add-subdomain:521

STEPS TO REPRODUCE

- Go to a subscription
- Add a new subdomain
- Enter the name of the subdomain

ACTUAL RESULT

The document root field is empty

EXPECTED RESULT

A proposed document root

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
That's odd. I've tried Firefox and Chrome (latest versions) on macOS, and they both have the same issue.
Even in private/incognito mode without any add-ons.
 
No worries, I think that when you post an issue here it is very likely a real issue and worth a detailed examination. I just wanted to give feedback what the situation is on our servers here. I hope this can be sorted out.
 
Fixed in the extension htaccess to nginx:
1.1.2 (03 October 2022)
The extension no longer produces errors in the console and does not block auto-filling of the "Docroot" field. (EXTPLESK-3973)
 
Back
Top