Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@smurfix I think you need to fix TLS setup. Currently, you have wildcard at wrong place:
TLS wildcards work only for one level up. Due to this, you need to set up additional TLS wildcard certificates for DNS Names one subdomain higher:
*.ipfs.ipfs.cyou
and*.ipns.ipfs.cyou
.See https://docs.ipfs.tech/how-to/address-ipfs-on-web/#subdomain-gateway
You can reproduce with below:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm already working on it. Unfortunately my DNS secondaries sometimes decide not to listen to update notifications.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed, now uses working wildcard certificates.