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

veresk.ruslan.org are not reachable via HTTP #2

Closed
huksley opened this issue Jul 18, 2020 · 2 comments
Closed

veresk.ruslan.org are not reachable via HTTP #2

huksley opened this issue Jul 18, 2020 · 2 comments

Comments

@huksley
Copy link
Owner

huksley commented Jul 18, 2020

Due to API Gateway peculiar support for custom domains, no redirection are done to HTTPS version, veresk.ruslan.org:80 simply refuses connection.

curl -v http://veresk.ruslan.org
* Rebuilt URL to: http://veresk.ruslan.org/
*   Trying 34.250.60.85...
* Connection failed
* connect to 34.250.60.85 port 80 failed: Connection refused
*   Trying 52.214.31.221...
* Connection failed
* connect to 52.214.31.221 port 80 failed: Connection refused
*   Trying 52.209.162.7...
* Connection failed
* connect to 52.209.162.7 port 80 failed: Connection refused
* Failed to connect to veresk.ruslan.org port 80: Connection refused
* Closing connection 0
curl: (7) Failed to connect to veresk.ruslan.org port 80: Connection refused
@huksley
Copy link
Owner Author

huksley commented Jul 18, 2020

@huksley
Copy link
Owner Author

huksley commented Aug 13, 2020

Clarification: only regional domains does not support HTTP to HTTPS redirection. Switching to edge domain solves this.

@huksley huksley closed this as completed Aug 13, 2020
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

1 participant