Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SSL errors on all non-www subdomains #241

Closed
10 tasks
kauffj opened this issue Oct 24, 2017 · 5 comments
Closed
10 tasks

SSL errors on all non-www subdomains #241

kauffj opened this issue Oct 24, 2017 · 5 comments
Assignees

Comments

@kauffj
Copy link
Member

kauffj commented Oct 24, 2017

Domains like https://abc.lbry.io will serve the website, but trigger an SSL error.

Internal Use

Acceptance Criteria

Definition of Done

  • Tested against acceptance criteria
  • Tested against the assumptions of the user story
  • The project builds without errors
  • Unit tests are written and passing
  • Tests on devices/browsers listed in the issue have passed
  • QA performed & issues resolved
  • Refactoring completed
  • Any configuration or build changes documented
  • Documentation updated
  • Peer Code Review performed
@lyoshenka
Copy link
Member

can't fix this till letsencrypt supports wildcard subdomains: https://letsencrypt.org/2017/07/06/wildcard-certificates-coming-jan-2018.html

@ghost
Copy link

ghost commented Nov 24, 2017

Would it be possible to script something to provision the directory with a rewrite condition in your scheme? Apache/PHP?

@kauffj
Copy link
Member Author

kauffj commented Nov 29, 2018

Assigning to @nikooo777, this is server/ops related. Niko if you don't know anything about this please work with Grin to learn.

@kauffj kauffj removed their assignment Nov 29, 2018
@nikooo777
Copy link
Contributor

This issue is easily solved by adding a wildcard certificate (now supported).
For this to be done I should first tackle this issue: https://github.com/lbryio/ansible/issues/7

@nikooo777 nikooo777 added the consider soon Discuss this issue at the next planning meeting, then remove this label label Dec 6, 2018
@alyssaoc alyssaoc removed the consider soon Discuss this issue at the next planning meeting, then remove this label label Dec 19, 2018
@nikooo777 nikooo777 added this to the Dec 25th (SDK) milestone Dec 26, 2018
@nikooo777
Copy link
Contributor

Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants