• 11 Posts
  • 198 Comments
Joined 2 years ago
cake
Cake day: July 21st, 2023

help-circle
  • Yeah, first try your ISP to see if you can get a dynamic or fixed IP instead. Check if their website/FAQ mentions dynamic IP or cgnat. They might outright reject it, or try to upgrade you to an extortionate business package though. I signed up for my service and checked the cgnat before signing up but they hadn’t got around to updating their website that they changed their policy. After the surprise of being behind cgnat and after screenshotting their own website, I complained and hit upgraded to a higher level package for free.

    You can use tailscale to get around it, but then you need to install it on all devices and login. You can use cloudflare tunnels and think you can set it to not require login for some services. Both rely on third parties. Both are also safer than exposing directly to the public internet.

    If you want full control, you have to rent a cheap vps and setup a tunnel between that and your home server, then use the public IP of the vps for your services. Wireguard is probably the best choice for VPN. You could try pangolin, which is an open source cloudflare tunnel so is more complicated than a VPN but also includes a reverse proxy.


  • In an ideal world this should be the case but I can’t afford to do this practically and my business is a service, based on UK laws and requirements, available to UK residents only. The website is for information only and nothing is new or interesting to anybody but a few potential clients, and if theyre looking at it on holiday, theres something wrong with them! Nobody is going to reach out based on my website from abroad and if they did, I would not trust them at all. They would reach out through personal contacts or linkedin. If the bots stop spamming my site or server, I can stop limiting it.


  • Another option to reduce (but not eliminate) this traffic is a country limit. In cloudflare you can set a manual security rule to do this. There are self hosted options too but harder to setup. It depends what country you are and where your users are based. My website is a business one so I only allow my own country (and if on holiday I might open that country if I need to check it’s working, although usually I just use a paid vpn back to my country so no need). You can also block specific countries. So many of my blocked requests are from USA, China, Russia etc




  • You could be behind CGNAT - I’m not sure the best way to tell but it could be the reason.

    I would also highly recommend buying a cheap domain to use - it would be the price of a coffee per year but makes life so much easier and you don’t have to depend on duckdns. You can buy through cloudflare, porkbun or many other options which you can search for a good DDNS service to update them.




  • A small percentage of humans are knobs, so if you split into drivers, bikers, cyclists and pedestrians, then within each one there are knobs. I regularly see all go through red lights, go the wrong way up a road, don’t give way etc.

    The impact of these are different though. Drivers kill, and can kill other drivers and anyone else on the road. Motorcycles can kill cyclists and pedestrians but are more likely to be killed themselves by drivers. Cyclists can hurt and even kill pedestrians (although lower chance), and can be killed by drivers and bikers. Pedestrians are just exposed as fuck.

    We should design the roads to reflect that - pedestrians first, [transit maybe here?] cyclists, bikers, then drivers.

    I think bikers should be factored in and in some cases fuckcars includes them as victims of car brained culture (and acknowledge they are smaller, less harmful up the environment etc) and in some cases say fuckbikes (they can kill you and do emit green house gases).



  • In what sense? It’s pretty hard to compare a Saturday afternoon in Trafalgar Square vs Canary Wharf vs Burgess Park to a Tuesday morning rush hour time in those same places.

    It’s a massive global city with anything you can possibly want to do or eat, with some amazing areas to some shit areas and everything in between! It can sometimes be crazy, hectic, busy, expensive but theres a reason went millions of people live and/or work or travel there every single day.

    It’s not for everyone but that’s fine. I know people who can’t stand it, and I personally can’t imagine living anywhere else. Most people fall somewhere in the middle though. Everything in life is a compromise in some way.

    Currently, it’s colourful and busy with Christmas lights, parties and markets. Crime feels the same it’s ever done (generally pretty safe but you have to be careful). It’s so much nicer to walk /cycle places than it used to be with wider pavements, pedestrian areas, cycling lanes etc. If you’re driving, it’s horrible. The tube older lines are still horrible but new Elizabeth line is amazing. Some suburbs have lots of flags up, some have none at all. The cost of everything is crazy - £8-9 for a pint typically.








  • I’m sure you are far outweighed by users like me who keep one for when traveling away from home and working in public spaces (i do two days a week on average). Most days is no bandwidth and when there is usage its pretty low as limited to the public WiFi so just syncing files for local changes and general internet use / research. I could do and sometimes use a VPN to my home server but I don’t want the risk I can’t work anywhere if something happens.


  • Sorry, the post didn’t have the formatting I expected and is generally quite unclear now I’m reading back through it. I was trying to point out a few different things that I’ve had to learn the hard way when things go wrong! You learn the terminology to search for or have to search for lots of acronyms until you learn them haha.

    Public IP

    So your server is on a fixed IP address. Do you men locally that the machine has a fixed IP within your home lan setup (like e.g 192.168.1.10) or is your public IP fixed (this will depend on your ISP)? Most home providers, like mine, have dynamic IP so every once in a while my public IP will change so everything would go down as my DNS is pointing to the wrong address. Some providers use CGNAT which is even worse and won’t accept any connections originating from outside.

    If dynamic, you can use a DDNS tool like cloudflared to keep checking your public IP and updating your DNS records if it changes. Your services will only go down for however long the polling on this is set. Note that cloudflared does a few things and this is just one one aspect of the tool.

    If you have CGNAT you have to use cloudflare tunnels or similar to create the permanent bridge to your server that all external requests can pass through even if originating from outside.

    Docker bridge networks

    Note this is not essential but can be actually easier to manage and keep more secure. It was hard to get my head around but once I did it was easier.

    You can create a bridge network so the containers you add to that network can talk to each other but the other containers can’t. It also means not opening ports in the docker compose so the system can’t access those containers directly using up ports. A container can have multiple networks too.

    For instance, my nextcloud main server is on proxy and nextcloud-internal networks. The other containers in that docker compose are on nextcloud-internal. My proxy manager (caddy) is on proxy. The various nextcloud containers can talk to each other on the internal network. My proxy and the nextcloud server can also talk to each other through the proxy network. My server cannot talk to any of them directly (unless you also expose ports). Caddy cannot directly talk to my nextcloud database container. Hope it make sense, I can share my docker compose files if helpful. After this info, my original message may make more sense.

    You probably expose ports for jellyfin so can access it locally through 192.168.1.10:8080 or whatever it might be.

    Reverse proxy

    This is separate to a tunnel but tools like cloudflared tunnels and pangolin combine them.

    The reverse proxy is something you setup to pick up a server domain address and deliver it to the requesting computer. It turns cloud.domain.com to 192.168.1.10:8000 and for a website delivers the HTML, images, php etc to client browsers. In the self hosting space it let’s you access different services on one domain (like www.domain.com, cloud.domain.com, request.domain.com as much as you like)

    I have caddy on docker but previously used nginx proxy manager, and for each public service I would setup a reverse proxy to the actual service. For my business website I tell it to send and domain.com and www.domain.com requests to my website in a different docker container. For nextcloud I tell it to send cloud.domain.com requests to my nextcloud server container on its port (on proxy network - see above, in caddy I say reverse proxy to nextcloud-server:80 but if exposing ports it could be your internal server IP like 192.168.1.10:8000 or whatever you are using).

    Tunnel

    This is just connecting two servers or clients and gives them a local IP on each end that can be used to encrypt and tunnel those connections over the internet.

    I don’t actually have a tunnel for my external services as I use my business VPS. I do have a tunnel between my home server and my VPS to create an encrypted and usable tunnel between those separate internal networks.

    I believe cloudflare tunnels and pangolin work the same way, where a user visits your service.domain.com and the service expects you to login. If logged in, it will forward the requests to your home server through an encrypted tunnel (so your ISP and others can’t see it, and your users never see your public IP address), and it also reverse proxies the request to the correct service on your server (like nextcloud). It does both jobs for you. The authentication stage might be optional, I’m not sure.

    It is easier to use these but you’re more tied in to one service.

    Cloudflare proxy

    If you use cloudflare DNS and opt into their proxy, they will hide your home server’s public IP from external users using services through your domain. If you lookup a domain like “dig domain.com” in the CLI, you will see Cloudflared public IP instead of your own. The connection packets will go to Cloudflare, who internally change it to your public IP so the end client cannot see it. It does mean they can track all your header information and unencrypted traffic, and if it goes down nobody can access your services externally using the domain.

    Incidentally, I notice some IPTV services use this to try to hide their public IP but in reality, broadcasters could get the real IP from Cloudflare, especially with a court case.