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 and Always Up

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

  • SSL and Always Up

    I have a client using AlwaysUp with the v8 server. Site has been working fine. They just bought a Verisign certificate and are having a problem.

    They open a second copy of AS and install the cert files, which includes a chain file. When they cycle AlwaysUp, or start a second copy from the desktop again, an error is displayed
    "Unable to read certificate file for SSL".

    When the CSR was generated a blank password was used. Is this a problem?

    Any issues to be aware of with AlwaysUp?

    Bill.

  • #2
    Re: SSL and Always Up

    Lenny showed me a trick - make sure the extension is CRT, then double click the certificate file to get a description of the certificate. In my case a message said this was not a valid certificate.

    So now we go back to Verisign.

    Bill.

    Comment


    • #3
      Re: SSL and Always Up

      Could you document your process in this case. I have a somewhat incomplete document on my website regarding ssl. I'd like to compare your process to what I have listed, redraft the document and then put up here for public use.
      Steve Wood
      Join the ALPHA DEVELOPERS NETWORK
      There is no Cloud. It's just someone else's computer.
      Web - Mobile - Hosting - Products - Frameworks - Developer Resources
      AlphaToGo | IADN (100% Alpha Anywhere Websites)

      Comment


      • #4
        Re: SSL and Always Up

        Got some more testing code from Lenny, but have not reached a solution yet. I am sure we will get it working. I just hope we ultimately know what the problem was. Will post again.

        My previous uses of SSL were deceivingly simple.

        Bill.

        Comment


        • #5
          Re: SSL and Always Up

          I gave Bill some Xbasic that can be used to validate a certificate, but that's actually the hard way. There is a test function as part of Alpha Five - ssl_test_cert()

          Code:
          'for a certificate with no password or chain file
          ?SSL_test_cert("c:\ssl_certificates\test.cert", "c:\ssl_certificates\test.key")
          = Canceled = .F.
          Code = 0
          Error = .F.
          NativeCode = 0
          NativeText = ""
          Success = .T.
          Text = "Success"
          
          'with a password
          ?SSL_test_cert("c:\ssl_certificates\test2.cert", "c:\ssl_certificates\test2.key", "password")
          = Canceled = .F.
          Code = 0
          Error = .F.
          NativeCode = 0
          NativeText = ""
          Success = .T.
          Text = "Success"
          
          'with a chain file
          ?SSL_test_cert("c:\ssl_certificates\test3.crt", "c:\ssl_certificates\test3.key", "password", "c:\ssl_certificates\test3_chain.crt")
          = Canceled = .F.
          Code = 0
          Error = .F.
          NativeCode = 0
          NativeText = ""
          Success = .T.
          Text = "Success"

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

          Comment


          • #6
            Re: SSL and Always Up

            The problem turned out to be that the cert file was in IIS format, and needed to be in Apache format. The message we got in this case was
            "Unable to read certificate file for Secure Sockets Layer" (attached)

            Does not point you straight to a solution, so take note.

            I had done a Godaddy cert before and had no problem, so maybe they default to Apache format (can't remember). Verisign has a long pick list.

            I don't fully understand the double click trick. Seems that if the cert is in apache format then info about the cert is correctly displayed. If the cert is in IIS format, then you get a message that says it is not valid. However, if you are actually using the cert for IIS, not Alpha, the cert does work correctly. The fact that you only get a good display if it is Apache is good for us, but be mindful if you are in a mixed environment. The Verisign chain file always displayed correctly with a double click, so maybe that is always Apache format.

            Bill.

            Comment

            Working...
            X