Wireguard.
Because I would like to self-host everything myself, so why should I use another 3rd party service?
did you bind one of them to any host? If not you can delete any of them, then use the other one.
You have to set the docker container name as the destination, not the host IP.
Test everything from the beginning.
# check your FQDN is set up correctly.
$ nslookup 1.1.1.1
$ nslookup 8.8.8.8
# Test your web host from out of the docker host.
$ curl -v http://your_fqdn
# test your web host on the host machine.
$ curl -v -H "Host: your_fqdn" http://localhost
# check if your port is exposed if you map it.
docker ps | grep
# check if your mapped port is listening on the docker host
netstat -tlnp | grep
#check if your container is reachable by NPM.
docker exec -it bash
[root@docker-278f29455e29:/app]# apt update && apt install netcat
[root@docker-278f29455e29:/app]# nc -zv
if NPM reaches docker, you're OK.
There are many things you have to check more, for example, NPM and your destination container should be in the same docker network.
# docker inspect | grep NetworkID
# docker inspect | grep NetworkID
They should be equal.
etc. etc.
if the Asus router has wireguard server capabilities, you're in luck.
on house B, port forwarding is not necessary because the router will handle it.
on house A, because pfSense will work as a client port forwarding is not necessary either.
https://hub.docker.com/r/gdomod/nginx-vod-live-hls
tried this one and it works.
docker run -it --rm --name nginx -p 1937:1935 -p 8035:80 -v "/storage/videos/":/videos gdomod/nginx-vod-live-hls:latest
to play vod.
http://:8035/vod/.mp4/index.m3u8
- install wireguard on both ends, one will be the server other is the client.
- add necessary iptables rules on server and client.
- if you have a router, without gateway route destination network requests to the local wireguard host.
- if you have a router, route destination network requests to local wireguard host.ient in the local network. ( your local wireguard host as gateway)
I'm using Nextcloud, it's forked from Owncloud.
Of course, it's possible to link your database to a local machine. Why do you want to store your database on a local machine? Why don't you want to put the database together with Owncloud?
Your steps should be like this with my approach.
- Install wireguard software on VPS.
- Install wireguard client on your local machine as a service.
- Install database software on your local machine and use the IP address of wireguard client IP as management.
- Install Owncloud on your VPS. While installing it will ask for the database IP address, so point it as wireguard client IP address.
I don't know if you look at the awesome self-hosted list;
https://github.com/awesome-selfhosted/awesome-selfhosted#human-resources-management-hrm