Add a landing page for people who cannot reach their own server - #63
Merged
Conversation
The two existing landing pages argue that self hosting is worth doing. That is the wrong argument for someone who already self hosts and whose server simply cannot be reached from outside. That is the audience the subscription is actually for. The relay, the domain with automatic DNS updates, the certificate and the mail relay are precisely the four things a self hoster cannot provide themselves: behind DS-Lite or CGNAT there is no port to forward, a changing IP breaks any name, TLS needs a domain you control, and mail from a residential address is rejected. The forum says the same. Ordered by views: NAT loopback 1877, certificate renewal on a custom domain 1073, a router change breaking access 999, an expired certificate after renewal 836, CGNAT access 738. A search for CGNAT also returns users asking for Tailscale as an app, which is the relay we already sell. So the page leads with the problem and answers it, rather than opening with forty apps. Variants can now override the bullet points, since a shared list written for the undecided says nothing to someone with a specific fault. German and English, both noindex like the existing landing pages, since these are ad destinations rather than pages to be found.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The two existing landing pages argue that self-hosting is worth doing. That is the wrong argument for someone who already self-hosts and whose server simply cannot be reached from outside — which is the audience the subscription is actually for.
Reading
redirect/backend/relay/tiers.goandutils/config.go, the subscription is relay traffic (1 GB free / 10 GB pro / 100 GB max), outbound mail relay, asyncloud.itdomain with automatic DNS updates, and a certificate. Those are the four things a self-hoster cannot provide for themselves: behind DS-Lite or CGNAT there is no port to forward, a changing IP breaks any name, TLS needs a domain you control, and mail from a residential address is rejected everywhere.The forum agrees. Ordered by views: NAT loopback 1,877; certificate renewal on a custom domain 1,073 (19 replies); a router change breaking access 999; an expired certificate after renewal 836; CGNAT access 738. Searching the forum for CGNAT also returns users asking for Tailscale as an app — a third-party tunnel to solve what the relay already does.
So the page leads with the problem and answers it, instead of opening with forty apps.
/de/remote-accessand/en/remote-access, bothnoindexandbarelike the existing landing pages, since these are ad destinations rather than pages to be foundThree tests: the headline leads on the problem, the points answer access rather than listing apps (in both languages), and price/CTA remain shared. 66 passing.