Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Web Sockets Cannot connect

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Web Sockets Cannot connect

    So here is my issue: I placed the web sockets demo (with no changes) on a test page. I enabled websockets in my project properties and for the port I put +10
    My project is hosted with an application server using SSL (port 443)
    When I load the page, I get this error:
    Test.a5w:1694 WebSocket connection to 'wss://www.nwcopro.com:90/?id=5834CCC6-B10B-4CB0-8E81-57AAE31ED053&subscribe=messageboard,alpha' failed: Error in connection establishment: net::ERR_CONNECTION_TIMED_OUT
    So - this must mean SOMEHOW, node.js is using port 80 as it's starting point for an wss connection.

    I asked Selwyn about this - he asked if I was using the pre-render option - that's a negative, this is the websockets demo that AS created unaltered.
    He also stated that there is an issue with websockets and load-balancers - again, that's a negative as well as I am not using one.
    I use always up and RDP Guard and that's about it.

    I think my first question is if anyone is using websockets on a secure server? If you put +10 do you get port 90 or 453? Does anyone think that should matter? I would assume there is an issue with the certificate at this point and the port would be irrelevant...thanks for any input!
    NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

  • #2
    Re: Web Sockets Cannot connect

    We have experienced the same behavior (same set up as you ) with the exception that the port was set to an arbitrary number ( such as "1212") instead of a +10...
    It would work intermittently but whenever it failed the browser was always requesting it on port 90, the same as your time out error.

    Did you ever figure out what was causing this?

    Comment


    • #3
      Re: Web Sockets Cannot connect

      No, I would encourage you to submit a ux for testing and review. Selwyn did not have an answer for me, other than it was weird. Interesting that it worked sometimes.
      NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

      Comment


      • #4
        Re: Web Sockets Cannot connect

        Jeff, are you running two instances of the web server or perhaps a custom config file?
        NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

        Comment


        • #5
          Re: Web Sockets Cannot connect

          I am still wondering WHY this will not work on my server. Websockets work correctly in live preview so all I can figure is that there is something missing on my server that is on my local machine. In other words, I thin maybe there are some node files missing on my remote server that are present on my local machine, perhaps in the live preview folder?
          The error is: failed: Error in connection establishment: net::ERR_CONNECTION_TIMED_OUT
          but as I said, the component works as expected using live preview.

          In the project properties, I have +10 set for the port and the console is showing me that it's using port 90 which is odd for a server using 443. Seems like it should be using 453 as a port. Websockets would be awesome if they worked for me!
          Any thoughts are appreciated!

          btw, the component is the websockets demo UX - no changes...
          NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

          Comment


          • #6
            Re: Web Sockets Cannot connect

            Is port 90 open for access in your server (not Alpha or Web socket server)

            Ken

            Comment


            • #7
              Re: Web Sockets Cannot connect

              I am not sure, but regardless it doesn't connect via any port I assign. The main issue with bringing up the port was that the application is served via https (443) so I would think the port would be 453 using wss://domainname...
              In others words the connection is using wss for the websocket connection, but assigning 90 as though it were using 80 as a starting point.
              NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

              Comment


              • #8
                Re: Web Sockets Cannot connect

                using netstat i confirmed the port ( I chose 8083 as a test) is listening so not sure why there is a timeout
                NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

                Comment


                • #9
                  Re: Web Sockets Cannot connect

                  Did you also check firewall blocking? Your software listening some port does not function properly if firewall blocks traffic in and out.

                  Comment


                  • #10
                    Re: Web Sockets Cannot connect

                    Since I have RDP Guard installed, I am not entirely sure if that has anything to do with it. I also stopped the AS server on port 80 and just tried 80 - but again, using netstat I could see the server was listening on port 80. I am looking into the server logs to see if there are any logs of the attempted traffic connection. Being a novice in this area, I am not sure exactly where to look for possible problems.
                    NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

                    Comment


                    • #11
                      Re: Web Sockets Cannot connect

                      Better option than RDP Guard is to use external firewall. For example AWS and Leaseweb VPS Cloud has it without extra cost.

                      Web socket server has nothing to do with WAS. They are two different servers and can not for example listen same port. There would be an error when you start server. Normally ports (in server like 2016) are closed and you have to explicitly open them for use. So you have to check this in windows firewall and open ports if needed. Remember also close them if you do not need them anymore. When you are testing you can shut down RDP Guard.

                      Comment

                      Working...
                      X