Confirm the prompt belongs to the intended site
A WordPress connection-information prompt calls for a filesystem-permission check, not an automatic entry of hosting credentials.
Pause at a connection-information prompt until the site owner confirms the intended filesystem route. Check that you are on the real site’s authenticated admin URL and know which component is being updated. WordPress’s Filesystem API may ask for FTP or SSH details when it cannot use direct filesystem access for that operation. The prompt does not prove that any particular Novasean transfer method is included or that your main panel password is appropriate.
Take a current backup and record the component version before continuing. This guide stops at the pre-update connection decision; a later stale maintenance marker or plugin fatal error needs its own recovery path.
Check the account’s approved write method
Ask the application owner what method normally deploys updates to this installation. If the purchased account exposes an authorised FTP, FTPS or SFTP identity for that exact site, confirm its protocol, hostname and scope from the trusted account controls or operator. Do not send the credential to support, store it in wp-config.php to avoid a prompt, or use a personal client-area login without an approved reason. WordPress’s Filesystem API documentation distinguishes direct file access from transfer-based methods; the choice can depend on ownership and permissions.
If no approved transfer identity exists, or the prompt repeats after correct account details, stop. Ask support to review the installation’s account-scoped file ownership and effective write path. Do not recursively change ownership, set broad write permissions or force a filesystem method in application configuration without the operator’s assessment.
Run one controlled update after the route is confirmed
Once the owner and operator agree a legitimate method, update only the intended component using the supported WordPress flow. Watch the result instead of submitting credentials repeatedly. A successful connection is not proof that the update finished. Record any reported failure, component version and time. If an update partly applies, use the application owner’s backup and official recovery procedure rather than trying more permission changes.
Check the resulting site and retain rollback evidence
Confirm the installed version in WordPress and test the public home page, one affected feature and the admin area from a fresh session. If the update fails or the prompt returns, preserve the error and ask the responsible application owner or platform operator to check the specific file route. Do not remove a working access method until the new route is proven.
For example, after an authorised ownership repair, retry only the named update and check its installed version and affected page. If the prompt returns, retain the error rather than entering broader credentials.
Frequently asked questions
Should I enter my WHMCS password? No. The prompt concerns WordPress filesystem access; use only an authorised credential for the exact installation and method.
Would chmod 777 stop the prompt? Broad write permission is unsafe and does not establish the correct account ownership or update method.
Sources and technical references
Related guides
Was this guide helpful?
If you accepted optional analytics, your Yes/No answer and this guide’s page address are sent to Google Analytics. No written feedback is collected. Read our privacy statement or change your choice in .
Need help with your service?
Open your client area or contact Novasean. Describe the symptom and checks you have performed. Keep passwords, recovery codes and private keys out of your message.