openworm / openworm/OpenWorm

The openworm.org SSL certificate is valid for github.com, *.github.com, but not openworm.org. browser.openworm.org sends an empty reply over HTTPS.

Open
#305 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
3.1k
Forks
244
PR merge metrics
No merged PRs in 30d

Description

If this issue is intended to be a bug report, please fill out the following:

Expected behavior

Visiting https://openworm.org should not display a browser warning

Visiting https://browser.openworm.org , linked from the https://openworm.org homepage, should return a response.

Actual behavior

Visiting https://openworm.org displays a browser warning:

image

Visiting https://browser.openworm.org/ sends an empty reply:

image

The https://docs.openworm.org/ subdomain works and has a valid certificate 👍

Steps to reproduce the behavior

(curl https://openworm.org && echo "OK") || (echo "Not OK :(" && exit 1)
(curl https://browser.openworm.org && echo "OK") || (echo "Not OK :(" && exit 1)

curl: (60) SSL: no alternative certificate subject name matches target host name 'openworm.org'
More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
Not OK :(

curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to browser.openworm.org:443
Not OK :(


If this issue is intended to be a beginner issue, please add all of the following:

  • Requirements are clearly specified
  • Links to relevant "getting started" documentation
  • Tagged as "beginner"
  • Tagged with language skill needed to complete
  • Level of difficulty:
    • Trivial = Changing one-line of code somewhere.
    • Standalone = Changes & Development do not affect other components of project. Tasks can be on a critical path, but probably should not be.
    • Simple = from 2 hours work to maybe a week’s work (Thinking + Coding)

(not sure how to fill out the above)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the two curl commands in the issue for openworm.org and browser.openworm.org, then compare their results with the working docs.openworm.org subdomain. Done means openworm.org presents a valid certificate and browser.openworm.org returns a response over HTTPS.

Written by the indexing model from the issue text.

Assessment

Domain
infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.