Weird HTTPS behaviour

🪳 Bug Reports
1

Hey ENS team,
I’ve published contents to 3 different subdomains that didn’t work at all via .eth.link TLDs until around 30 minutes after the Ethereum transactions went through. I can now (30 mins later) access all 3 domains without HTTPS. It’s crucial that all of these 3 work with HTTPS. I’d like to note that the main domain https://collectorshub.eth.link worked instantly with HTTPs.

The Ethereum Transactions:
https://etherscan.io/tx/0x7288cca0f26e8dd2a67d38ae496737b6907269eb5074374b3a58bd722f17e29c
https://etherscan.io/tx/0xde536c749becb67af6c4ed581f62045274b519e1bcea682c440d1643266a1916
https://etherscan.io/tx/0x32a68864966669acaa8c50f5cb1b78de81f78b1de60685c7de10f4b92a06a778

after_30_mins
after_30_mins772×573 34.4 KB
first_30_mins
first_30_mins704×478 18.5 KB

2

Unfortunately, due to the way SSL wildcard certificates work, we can only support SSL on 3LDs (foo.eth.link). We don’t have valid SSL certificates for subdomains.

1 Like
3

Any tutorial how I can purchase and link my own SSL certificate? Or is there no way at all to solve this SSL issue for the subdomains?

4

There’s no way to store the private key so that only the eth.link servers can access it - so unfortunately there’s no solution for SSL on subdomains at the moment.

1 Like