Issue Unable to log in to Plesk dashboard

[sitenet]

Server operating system version

ubuntu 20.04

Plesk version and microupdate number

18.0.48

Hi sometimes when trying to log into Plesk, I am getting error: ApiFetchError: Failed to fetch.

https://imgur.com/9PCNuUs

After inputting username and password, I am getting that error but then after some time I can log in and then again, the error would appear when I try to log in the next time.

What is causing the issue?

Some other details if required - Using ubuntu 20.04. VPS has 2gb ram, 2core cpu, 60 gb hdd, 2gb swap memory. Only 1 website is live. Domain is routed behind cloudflare.

How to fix?

 

[vikK]

try to use ip:8443 to login and see if it works.

 

[sitenet]

Seems to be working so far as of now. Lets see

 

[bfts-gc21]

Hello there, I am also getting this error, and adding the :8443 is not working for me, ping to server is reachable. no clue what to do.

 

[Peter Debik]

@bfts-gc21 Have you checked that port 8443 is open in your local network? For a test, disable Wifi on your smartphone so that your phone is using a cell instead of wifi, then open the page from your smartphone. Does that work?

 

[bfts-gc21]

Tried on cell phone no wifi and nothing

 

[Peter Debik]

@bfts-gc21 Maybe the psa service, sw-engine or something associated is not running. You'll need to login to the Linux console and check it. As that is a completely different situation than in this thread I kindly ask you to open a new thread for your question.

 

[bfts-gc21]

Yes seems to be fixed.. support tech found something else wrong.. not sure what it was. Thanks

 

[Peter Debik]

Plesk is aware of this intermittently appearing issue. It is not reproducible reliably, but from a number of cases it was possible to estimate what reasons could be. This issue is under investigation and will for sure be fixed in one of the nearer updates.

 

[DaiKen]

Plesk is aware of this intermittently appearing issue. It is not reproducible reliably, but from a number of cases it was possible to estimate what reasons could be. This issue is under investigation and will for sure be fixed in one of the nearer updates.

It is almost November 2023 now, and the problem still exists. Very annoying!

 

[Peter Debik]

@DaiKen The best you can do is to open a support ticket for your case.

 

[MartinT]

Hi

I had this fetch error some days ago and it was caused be fail2ban. I uninstalled it and reinstalled it and it was gone. Maybe this helps.

 

[Iván Jaimes]

More than half of the year 2024 and also getting the same or similar error on multiple occasions, not only when logging in, but also when navigating through the different configurations of the control panel.

TypeError
undefined is not an object (evaluating 't.find((({id:e})=>e===h)).options[m].toLowerCase')

Type    TypeError
Message    undefined is not an object (evaluating 't.find((({id:e})=>e===h)).options[m].toLowerCase')
Stack trace   
c@https://11.111.111.111:8443/cp/javascript/views/smb/web/php-settings.js:1:10829
Cl@https://11.111.111.111:8443/ui-library/plesk-ui-library.min.js:35:62771
ko@https://11.111.111.111:8443/ui-library/plesk-ui-library.min.js:35:119281
yc@https://11.111.111.111:8443/ui-library/plesk-ui-library.min.js:35:108529
bc@https://11.111.111.111:8443/ui-library/plesk-ui-library.min.js:35:108457
vc@https://11.111.111.111:8443/ui-library/plesk-ui-library.min.js:35:108320
cc@https://11.111.111.111:8443/ui-library/plesk-ui-library.min.js:35:105482
cc@[native code]
Vs@https://11.111.111.111:8443/ui-library/plesk-ui-library.min.js:35:46633
rc@https://11.111.111.111:8443/ui-library/plesk-ui-library.min.js:35:102612
ti@https://11.111.111.111:8443/ui-library/plesk-ui-library.min.js:35:68089
ti@[native code]
@https://11.111.111.111:8443/cp/javascript/vendors.js:20:4743
@https://11.111.111.111:8443/cp/javascript/vendors.js:20:5658
forEach@[native code]
ne@https://11.111.111.111:8443/cp/javascript/vendors.js:42:18734
ie@https://11.111.111.111:8443/cp/javascript/vendors.js:42:19984
@https://11.111.111.111:8443/cp/javascript/vendors.js:42:25252

 

[Sebahat.hadzhi]

Hello, @Iván Jaimes. We are sorry to hear about the issue you are experiencing. The initially reported error in this thread has been fixed with the first update release of Plesk Obsidian 18.0.50. From what I can see the error you are encountering is indeed slightly different. What I would suggest is if possible to open a ticket to our support team for an investigation. To sign-in to support and open a ticket go to:

• https://support.plesk.com.

If you got your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative to get support directly from Plesk:

• How to get support directly from Plesk?

If that's not an option, please provide us with step-by-step instructions on how to reproduce the error on our end, along with your server OS and the exact Plesk version you are using.