Topic: Opera 10 & Server Manager

[ltwally]

I did a quick search on the forum and didn't find a result... so...

Anyone else unable to get into the server-manager (SME 7.4 fully patched) using Opera 10.0 ?

SME gives me this message when I try:

Your browser does not appear to support cookies or has cookie support disabled.
This site requires cookies - please turn cookie support on or try again using a different browser.

Cookies are enabled, and other websites seem to be using them just fine.  Odd.

I've tried this with a fresh install of Opera 10 on a clean machine, just to verify it wasn't something I'd done to my favourite browser.  Same result.

Older versions of Opera work just fine with the server-manager.  Even more odd.

Any ideas?  Anyone else have this experience?

[piran]

Any ideas?  Anyone else have this experience?

No and yes.

Firefox does that... particularly during enforced reboots/restarts when I had
not yet specifically opened an iteration of server manager in the browser.
Workaround with Ctrl-B and specifically re-opening that otherwise
unresponsive tab using its bookmark. Not just Opera 10. I don't usually use
Opera for the server manager so I don't have a workaround for that browser.
At a guess it's something to do with or in the way that Opera saves cookies.

[ltwally]

I use Opera for my primary browser, so I noticed this very quickly after upgrading it a week ago.

I forgot to mention that other browsers are perfectly capable of opening server-manager.

So, for whatever reason, Opera 10 dislikes the cookies that SME is setting.  Or SME dislikes the way that Opera 10 is doing cookies.  Either way, it's a unique experience to me.

It's just very odd.  If anyone knows of a fix, I'd certainly appreciate it!

Thanks!

[piran]

This worked here for me with Opera 10:
Delete the existing cookie (Tools | Advanced | Cookies | 10.0.0.1)
• instead of my normal https://10.0.0.1/server-manager/
• used https://(servername)/server-manager/
YMMV

[ltwally]

This worked here for me with Opera 10:
Delete the existing cookie (Tools | Advanced | Cookies | 10.0.0.1)
• instead of my normal https://10.0.0.1/server-manager/
• used https://(servername)/server-manager/
YMMV

That worked for me, too.  Thanks!