Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)OI
Posts
0
Comments
510
Joined
2 yr. ago

  • This - why add another machine into the equation?

    Or set up an account at Tailscale or similar. They let you have like 10 machines in your network w/o payment

    Or route to your home network through the vpn interface on the VPS. So you can reference the windows ip, rather than NAT

    Your current setup is very complicated. I did not check your rules at all but maybe you are setting up forwarding on your servers lan interface rather than the WireGuard interface.

    Also you don’t say much about how the VPS setup is. Do you Nat the other working services? What IP/host do you forward to? Are you rdp’ing from the VPS or is that also some form of forwarder/revproxy?

  • It’s mostly for home-points. It’s not likely to get passed. Also questioning the idea that Poland is to be a leading country in EU any day soon. It will be hard for Tusk to pass anything but what he can agree with pis.

  • It’s only legal if it’s required for your profession (like in aviation), it might threaten life or mean death (for instance a taxi driver), there are big non-lethal risks connected to the employee’s work (no idea on this one)

    As it’s a medial procedure so it has extra rules regarding that and the shielding of medical records from the employer.

    The company also have to discuss this with the workers show stewards before they choose to do testing, and other forms of action needs to be taken and be ineffective before you can move on to testing.

  • Yes - I like bind9 with views so I can serve external and internal from same instance. As I only have services for my own use 1 ns on my dynamic ip is enough for my home subdomain.

    Bind9 has ok scripting possibilities with rndc and nsupdate.

  • Like with most technology, init should be based on use-case.

    Some setups are not made for quick reboots and that’s ok. When all your container does is run ddclient you might find that even cron can work just as well as systemd.timers

  • Right - so the upstream server is a docker container on the same machine, and you proxy the connection to the servers up on the port forwarded through the magic docker iptables thingy. It might be here that you get the connection closed - maybe check logs on that. Don’t recall if it’s logged by default or you have to set it up

    There’s also the possibility of the web service not being proxy friendly

  • I’m not very familiar with nginx, I use haproxy for my reverse proxy or load balancing needs.

    Do the 504 get logged on the proxy? From your screen grabs it seems that nginx have a working connection to the upstream server.

    Maybe that website needs special settings that nginx can’t handle or is not set up for?

  • Without gpl source there would be no RHEL. If they want closed source there’s other kernels with userlands under proprietary licences or bsd-like, yet they went for the GPL one. To lucrate (?) on top of it.

    How many do you reckon would be using systemd if it was closed source? What about Wayland? I’m thinking mostly just you and their fanclub

  • Is this your internal domain name of the nas box, or are you trying to reach your gw’s ip though NAT?

    If you do a lookup of the domain name you try to enter - does that give the same IP as you use when successfully connect?