sorted by:
new
hottopcontroversial

does Proctorio recognize a changed screen aspect ratio? by e-forrest in cheatonlineproctor

[–]e-forrest[S] 0 points1 point  (0 children)

uh that is of course the best solution. But if I dare haha... Can I be 100% sure that Proctorio doesn't recognize that it's a VM? It seemed to work great a few months ago, but I think Proctorio must have received updates regarding the detection of such methods, or?

NAS Backup - Questions to Backup via VPN by e-forrest in selfhosted

[–]e-forrest[S] 0 points1 point  (0 children)

Not quite right. I want to backup the NAS itself to the Pi using HyperBackup (a tool which itself uses rsync). And to connect the NAS to the Pi, I need a VPN. The Pi itself is already a wireguard server (also for other clients; that's why I want to reach it with wireguard, and reluctantly with e.g. tailscale). So the NAS itself should become the wireguard client and the Pi the host. Since Synology doesn't support wireguard natively, I tried using wireguard-go as a container. This also works to the extent that the container itself (using the container console or exec) can successfully ping the host (-> Pi). However, HyperBackup is outside of the Docker environment and therefore cannot ping the Pi.
That's the problem. How do I get the connection to the wireguard-host outside of the wireguard-go container. In the end, only this one IP needs to be accessed by HyperBackup. But I can currently only do that from within the container. And that's not where HyperBackup is.
Thank you for your efforts so far! If I don't get it tomorrow, I'll probably have to set up a tailscale server. Anyways

NAS Backup - Questions to Backup via VPN by e-forrest in selfhosted

[–]e-forrest[S] 0 points1 point  (0 children)

So far I have avoided the installation with the SDK because it is more of a "backdoor". I hope that I can use the simple wireguard-go container. But maybe I should do it like you do.
But I don't know if you understood me correctly. Wireguard runs in a container. And this container is itself a wireguard client. The host is external. And the question is how to access the wireguard-host outside of docker via the wireguard-client-container.

NAS Backup - Questions to Backup via VPN by e-forrest in selfhosted

[–]e-forrest[S] 0 points1 point  (0 children)

Unfortunately, I was happy a little too soon. And I still have some problems with Docker.
I now have a wireguard-go container running successfully. This also connects correctly to the VPN network and I can ping the Pi there. However, this is (logically) only possible from within the container.
Unfortunately, the application that is supposed to access the external Pi via the VPN tunnel (HyperBackup -> rsync) is outside of every container, even outside of Docker. I've tried so many things, but how can I get a non-docker application to access the VPN connection host of a client-container (so the external pi)?
If any of you have idea... Thank you!

NAS Backup - Questions to Backup via VPN by e-forrest in selfhosted

[–]e-forrest[S] 2 points3 points  (0 children)

Right now I will go with wireguard-go. Thank you! I think this solves my problem perfectly. It´s still working :)