Resolved Immediate Logout after logging in using Safari Browser and OSX Sonoma

[iraweintraub]

Server operating system version

Ubuntu 22.04

Plesk version and microupdate number

Obsidian 18.0.55

Using Safari Browser and OSX Sonoma. Trying to log in to Plesk Obsidian 18.0.55, logs in and then immediately logs back out to login screen. Does not happen with Google Chrome Browser, same OS. Any ideas?

 

[learning_curve]

Using Safari Browser and OSX Sonoma. Trying to log in to Plesk Obsidian 18.0.55, logs in and then immediately logs back out to login screen. Does not happen with Google Chrome Browser, same OS. Any ideas?

It's not a Plesk issue. It must be the config / setup of Safari / your device.
We only use Mac devices and several of those are running MacOS Sonoma (the others are using iOS 17.02 and/or iPadOS 17.0.2). We have no issues logging in to Plesk Obsidian 18.0.55 via Safari / Firefox / Brave etc and to be fair, never have had, with all of the previous Plesk and / or MacOS / iOS / iPadOS releases.

Maybe you could check all of your chosen settings within Safari, plus, any anti-virus software that your might have chosen to use (that may impact on Safari) plus, the usual... clear related cookies & cache & then retry etc

 

[iraweintraub]

I changed the setting in Plesk: Tools and Settings, Session Management, Session Settings, "Allow IP address changes during a single session" - I checked that setting. It seems to work now without an issue.

 

[learning_curve]

I changed the setting in Plesk: Tools and Settings, Session Management, Session Settings, "Allow IP address changes during a single session" - I checked that setting. It seems to work now without an issue.

Great that you've confirmed that it was not a MacOS / iOS / iPadOS or Mac Device issue. That was always going to be the case to be fair.
In your original post, you didn't mention that you had a variable local IP address, when accessing your Plesk hosting account (e.g. via DHCP from ISP or VPN usage etc) as that would have helped, but you've now found the corrective action yourself, which is perhaps a better experience in the long term. FWIW That Plesk setting, is a basic Plesk setup requirement, which should be aligned with your pre-chosen access details. It's not a Plesk fault, it's just a config variable.