Vienna Symphonic Library Forum
Forum Statistics

200,193 users have contributed to 43,194 threads and 259,061 posts.

In the past 24 hours, we have 1 new thread(s), 10 new post(s) and 71 new user(s).

  • [SOLVED] Can't Connect to VA

    last edited
    last edited

    Hello,

    Since the last update (1.2.473), I’ve been unable to log in to Vienna Assistant. Next I enter my password, I get this error message (see below). Even if I click "Retry," nothing happens. After that, I receive a message from Google Chrome saying it cannot connect to the address 127.0.0.1 (localhost maybe ?)

    I’ve tried using Edge, Chrome, and Opera without success. I even attempted in safe mode with network support. Still no luck. Firewall disable.

    Any help is welcome 😉


  • Lodge a support ticket.


    Just a beginner
  • same


  • @Dominic-Laprise said:

    Hello,


    Since the last update (1.2.473), I’ve been unable to log in to Vienna Assistant. Next I enter my password, I get this error message (see below). Even if I click "Retry," nothing happens. After that, I receive a message from Google Chrome saying it cannot connect to the address 127.0.0.1 (localhost maybe ?)


    I’ve tried using Edge, Chrome, and Opera without success. I even attempted in safe mode with network support. Still no luck. Firewall disable.


    Any help is welcome 😉



    Today is the very first time in many years I'm having problems to connect to VA. I'll try later in the day.


  • Please try again, I just fixed the update that caused the last login issue.


    Ben@VSL | IT & Product Specialist
  • @Rokyo said:

    same

    Thanks Ben, resolved.


  • I am experiencing this problem as well. I just can't seem to log in. I just tried to install Vienna Assistant here. Pop-up blocker is disabled, firewall settings are okay. I don't understand what's going on. Retry just keeps the page loading forever while the app is waiting for authentication. Keeps timing out.


  • @193856 said:

    I am experiencing this problem as well. I just can't seem to log in. I just tried to install Vienna Assistant here. Pop-up blocker is disabled, firewall settings are okay. I don't understand what's going on. Retry just keeps the page loading forever while the app is waiting for authentication. Keeps timing out.

    Please get in touch with our support: support@vsl.co.at


    Ben@VSL | IT & Product Specialist
  • I am experiencing the same problem since the last update to Assistant 1.2.477. Cannot login in Safari 18.2 (macOS Sequoia 15.2). Safari is complaining that it cannot open the page http://127.0.0.1:31573/vslapi/callback ...... WebKitErrorDomain:305. I have logged out and in, cleared Safari Cache, allowed Popup blockers, firewall is off. This has worked for years without issues but seems to be broken now.


  • @206558 said:

    I am experiencing the same problem since the last update to Assistant 1.2.477. Cannot login in Safari 18.2 (macOS Sequoia 15.2). Safari is complaining that it cannot open the page http://127.0.0.1:31573/vslapi/callback ...... WebKitErrorDomain:305. I have logged out and in, cleared Safari Cache, allowed Popup blockers, firewall is off. This has worked for years without issues but seems to be broken now.

    Can you temporarely try to set another browser as your default browser? This sounds like Safari is blocking the reuired communication between website and Assistant. We will investigate this asap.


    Ben@VSL | IT & Product Specialist
  • @Ben said:
    @206558 said:

    I am experiencing the same problem since the last update to Assistant 1.2.477. Cannot login in Safari 18.2 (macOS Sequoia 15.2). Safari is complaining that it cannot open the page http://127.0.0.1:31573/vslapi/callback ...... WebKitErrorDomain:305. I have logged out and in, cleared Safari Cache, allowed Popup blockers, firewall is off. This has worked for years without issues but seems to be broken now.


    Can you temporarely try to set another browser as your default browser? This sounds like Safari is blocking the reuired communication between website and Assistant. We will investigate this asap.

    temporarily switching to MS Edge as the default browser "solved" the issue. I suspect that a recent macOS update might have tightened some Safari settings that are now conflicting with the way VSL Assistant works. I strongly suggest VSL to investigate and fix this issue as I'd like to keep Safari as my default browser on Mac.


  • @206558 said:
    @Ben said:

    @206558 said:


    I am experiencing the same problem since the last update to Assistant 1.2.477. Cannot login in Safari 18.2 (macOS Sequoia 15.2). Safari is complaining that it cannot open the page http://127.0.0.1:31573/vslapi/callback ...... WebKitErrorDomain:305. I have logged out and in, cleared Safari Cache, allowed Popup blockers, firewall is off. This has worked for years without issues but seems to be broken now.




    Can you temporarely try to set another browser as your default browser? This sounds like Safari is blocking the reuired communication between website and Assistant. We will investigate this asap.


    temporarily switching to MS Edge as the default browser "solved" the issue. I suspect that a recent macOS update might have tightened some Safari settings that are now conflicting with the way VSL Assistant works. I strongly suggest VSL to investigate and fix this issue as I'd like to keep Safari as my default browser on Mac.

    any updates on this???


  • why is this showing as being SOLVED when it actually is NOT???


  • now that turns out that VSL support team has fallen asleep on this topic, I googled a little bit and found this article:

    https://bugs.webkit.org/show_bug.cgi?id=284559

    It turns out that since Safari 18 any secure URLS that are preceded by only "http://" instead of "https://" are blocked by default, which seems to be the case for VSL assistant. This can be temporarily bypassed by turning off the Safari setting "Security->"Get a warning if the site you're visiting uses HTTP" .

    The final solution however, should be VSL to change the internal URL simply from http: to https: in their code for Assistant.

    ... although I doubt that ever anyone will read this or seems to care 😬


  • @206558 said:
    The final solution however, should be VSL to change the internal URL simply from http: to https: in their code for Assistant.

    This would also imply installing and trusting a certificate onto your local machine, which is a big no-no and why we can't use https in this case.
    Instead we are looking into using a custom scheme that hopefully works with Safaris as well.

    In the mean-time I recommend to change your default to an alternative browser.


    Ben@VSL | IT & Product Specialist