Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

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

SSL issue with Chrome browser

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

    #16
    Re: SSL issue with Chrome browser

    Larry,
    In your first post you said...
    My website is experiencing SSL issues that only seem to affect the Chrome browser. The error is intermittent - it only happens on some computers and only sometimes...
    What's the random error message the users are getting? And, when exactly does the error occur - sometime after being signed in or just when they first navigating to the site?

    Comment


      #17
      Re: SSL issue with Chrome browser

      The error message is that the system cannot get an SSL connection. It almost exclusively happens on login.

      They type in the username and password, hit login, then the server comes back with an ssl connection error.

      Refreshing the screen usually, but not always fixes the problem. However, we are dealing with the general public, so not everyone knows to do that.

      If I go to the site myself and login, it will work most of the time, but I also occasionally get the same error. I've logged in steadily (log out, log in, log out, log in) and sometimes I can't make it happen no matter what I do. Then I'll go back and the first time login it will fail.

      It is quite maddening.

      I called GoDaddy to see if they had a suggestion but they were also not able to duplicate the issue. However, after our call, the tech kept hitting the site until he got the error. (I was shocked when I got an email from him hours later.)

      That was when he suggested the error had to do with the SHA-1 root certificate. (So Kudos to Go Daddy support for sticking with it if they were right.)

      However, I have no idea how to eliminate just that one cipher from the list if that is even possible.

      This is a new issue (first appeared in December so far as I know), the site has been up for several years and not had this issue.

      He was saying that I should use only the certificate file with the bundle_g2 in the file name. But in Alpha it accepts that as the chain file, not as the ssl file. so I don't know how to base the ssl on just the one file.

      Comment


        #18
        Re: SSL issue with Chrome browser

        Larry, that this is a new issue backs up the GoDaddy tech's assertion that this is caused by an SHA-1 certificate. SHA-1 is no longer considered secure and browsers have been slowly tightening restrictions and many have begun to stop accepting them altogether.

        This is NOT the same as your SSL cipher suite - it is how your SSL certificate and the chain file it uses were signed when they were generated. There is no way to impact this by changing your cipher suite.

        As the tech suggested, you need to use a chain file that only has SHA-2 signatures, as well as an certificate with an SHA-2 signature. If your certificate uses an SHA-1 signature, you will need to have a new one issued. If your chain file uses any SHA-1 signatures, you will need to get an updated one from your vender. When GoDaddy says you need to use bundle_g2, that is the chain file, not the certificate itself.

        Lenny Forziati
        Vice President, Internet Products and Technical Services
        Alpha Software Corporation

        Comment


          #19
          Re: SSL issue with Chrome browser

          I did a complete re-key also and the issue still exists. So I guess I need to go back to Godaddy and see what they have to say about it again.

          Comment

          Working...
          X