Skip to content

SSL - WebSocket Error An invalid or illegal string was specified #694

Closed

Description

@itg-assistant

Corvin Meyer auf der Heide asked 2017-03-13 14:19:23 UTC

When enabling SSL in default.json I'm getting "Failed to Connect to Server" and the following lines in the debug-console.

WebSocket Error An invalid or illegal string was specified.

We have a valid authority ssl certificate installed on IIS-Server.

Best Regards

Corvin Meyer auf der Heide

Activity

  1. itg-assistant commented on Jun 12, 2026

    @itg-assistant
    Author

    Luca answered 2017-03-13 15:34:19 UTC

    Hi Corvin,

    It was fixed in .40, it was WJ-8096. I suggest to use .42 from the dev builds.

    See http://wisej.com/support/question/bug-with-https-websocket

    Thanks,

    Luca

  2. added
    BugSomething is broken or behaving unexpectedly.
    on Jun 12, 2026
  3. itg-assistant commented on Jun 12, 2026

    @itg-assistant
    Author

    Corvin Meyer auf der Heide answered 2017-03-13 15:44:16 UTC

    Hey Luca,

    I have already installed .42 . Have read the other question and thought it may has another reason, so I opened a new one.

    Best Regards

    Corvin Meyer auf der Heide

  4. itg-assistant commented on Jun 12, 2026

    @itg-assistant
    Author

    Luca answered 2017-03-13 16:14:12 UTC

    I can't reproduce. It is the error that was referred in the other thread. Looks like your installation is pick up the previous wisej.js or it's cached. I tried with FF and Chrome.

    You can try this:

    • Delete the browser cache

    • Delete \windows\temp\Wisej[app]\wisej.js (or simply delete all \temp\Wisej)

    Let me know.

  5. itg-assistant commented on Jun 12, 2026

    @itg-assistant
    Author

    Corvin Meyer auf der Heide answered 2017-03-13 17:30:23 UTC

    Figured out the dlls in bin and Release where still 1.3.37.0 instead of 1.3.42.0. Deleting and adding the references, rebuiding or cleaning had no Effect. Deleted the references, deinstalled wisej, installed 1.3.40.0, updated to 1.3.42.0 and added the References. Seems now I really have 1.3.42.0.

    Will make a deploy on the Server with the certificate in next days.

    Best Regards

    Corvin Meyer auf der Heide

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    BugSomething is broken or behaving unexpectedly.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions