

No. Need a domain to assign the endpoint to a subdomain. Cloudflare do have at cost domains so you can get them cheap and consider it the cost of the service.


No. Need a domain to assign the endpoint to a subdomain. Cloudflare do have at cost domains so you can get them cheap and consider it the cost of the service.


What are you looking to do? If it’s to do with a name server, you can delegate a subdomain and it’s children to be managed by another server using a ns record. This is actually how DNS works in general.


I checked and this does a similar thing. You can use WG to punch out a connection, and I have before. The linked program uses quic in a similar way to WG but doesn’t do any of the routing, just registers the connection to a hostname for application level forwarding.
It looks more that it provides an easy setup for an alternative.
Both methods can work on cg-nat as well since you are punching out.


We have had success with this on port 443 and it appears to do a good job on networks that only allow browsing. Usual problems with TCP based VPN still apply.


Honestly so much better when they moved away from the “everything is a floating window” interface. I can find stuff now.


Free ones are less common now (no-ip went paid.) Afraiddns is still free but requires regular account logins.


If anyone goes with finamp, sign up for the test version as it’s UI is significantly better than stable.


You need the web site to use a certificate from the same root authority as your client certificate. Otherwise browsers won’t present the certificate to the server. That means either warnings on connect or adding the root cert.
I do think if you are doing it with them in person it is doable to add it.


I recently did exactly this. Only works with the web UI, no apps support it, but working well and those without the cert just get a 400 error. Not sure if non technical tbh, since you will get warnings when adding your root certificates to any device, and that might scare some who don’t understand what it does.
Also set it up through wireguard, so can punch out of double NAT.


Don’t assume that proton won’t eventually want to sell up.


They said it wasn’t shared with the website. They didn’t say it wasn’t shared with anyone at all.


I’ve not used that software before, but a quick look at the guide makes me wonder if you have a https redirect in the nginx config. If that is hard coded to domain1 it will always redirect to it. Update it on the new config file to point to the right uri if that is the case.
Usually I setup with a single domain for the server, and use that for web mail, IMAP and SMTP certs. That way you don’t need to worry about the extra certificates needed for each domain (set your Mx to use the common name of your cert.)


Yea I didn’t think the post was that professional. Also the “unminified” version is just the minified with more white space. It still has poor names and no explanation of the binary blob.


Forked from gitea. The owners of the project implemented a change to the pr system where by you had the sign an agreement that the code belonged to them. This was seen as an intent to relisense at some point. Devs that wanted it to stay open moved to forgejo.
Until recently you could swap forgejo in to your gitea data, but now they are incompatible due to divergence.


Recommendation would be that you want to set up your ssh so that it only accepts publickey authentication. You also want to make sure you are not using a proxied DNS value, as CF only proxies http requests.
Personally I didn’t bother to setup ssh access as https typically works fine.
I’m pretty sure the MSA just has a clause that says you can only provide accounts to adults. That way it’s up to your org to check.


If you are talking about the home page, I blocked the container for “featured content” using ublock, that kills short and news in the feed. If you get linked to a short, you can use a extension to redirect the URL to the normal watch player.


Even if you have a proper clean IP, running a mail server is a hassle imo. By far having a single relay to send is fine if you get things set right, but also dealing with incoming spam is just way more work than paying to have it hosted.
I much prefer paying for email hosting and just dealing with outgoing emails if needed.
Considering it shows on the capture widget, probably Settings -> Gaming -> Capture.
I moved away for self hosting email, but my advice would be to look at anti spam providers. Most can act as both an incoming and outgoing filter for your emails, and will hold on to email if your mailbox host is down. It also means for outgoing you don’t need to warm up an IP to have your messages accepted.
Of course you still need to setup SPF/dmarc/etc but it takes out some of the fuzzier parts of email deliverablity…