Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Does anyone else encounter problems when accessing SolusVM using Chrome?
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Does anyone else encounter problems when accessing SolusVM using Chrome?

adygadyg Member
edited February 2012 in Help

Chrome receives empty answers from the server when attempting to login into SolusVM, change root password, change the host name, etc. Everything works as expected in FF.

I initially thought it's just a provider specific issue, until today, when I got a new VPS from a different provider and the same problems occur. Does this happen to anyone else? If so, did you find a way around it (except different browser)?

Comments

  • Yes I do, when I used SolusVM with The Host House. Was only solved by using Firefox :(

  • I've been using various SolusVM panels with no problem in Chrome, which is my main browser. Using version 16.0.912.77 m

  • KuJoeKuJoe Member, Host Rep

    It is the https that breaks it. Use http with Chrome as a workaround. See my thread on their forums for more details.

    Thanked by 2adyg djvdorp
  • I've had this problem with multiple SolusVM instances and Chrome in the past. Solved by using a different browser.

  • @KuJoe unfortunately for me, it seems neither of the providers I use allow access to SolusVM via http. Guess I'll stick to using FF until Google comes up with a fix.

  • @adyg Are you using port 5353 instead of 5656 if they have not changed the port?

    Thanked by 1adyg
  • @dmmcintyre3 http & port 5353 works. Thanks a lot!

  • @adyg I've been encountering this error as well. I opened a ticket about it and was told it was a chrome issue and there was nothing that could be done about it...

    I don't completely understand how it's a chrome issue though when nothing else I visit with https:// has the error.

  • KuJoeKuJoe Member, Host Rep
    edited February 2012

    @Corey read my thread for details. Providers can fix the problem by using nginx instead of lighttpd also.

    Also, if somebody could link the thread it would be appreciated (hard to do on a phone).

  • Google just released 17.0.963.46 m which seems to fix the issue (at least for me)

  • I'm on 11.0.695 lol. Works fine for me.

Sign In or Register to comment.