forked from subspacecloud/subspace
-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Description
I am trying to run it behind traefik as a reverse proxy so I cannot use:
--network host
I am getting the following errors when starting the subspace container:
`+ export NAMESERVER=9.9.9.9
- NAMESERVER=9.9.9.9
- export DEBIAN_FRONTEND=noninteractive
- DEBIAN_FRONTEND=noninteractive
- echo 'nameserver 9.9.9.9'
- /sbin/iptables -t nat --check POSTROUTING -s 10.99.97.0/24 -j MASQUERADE
iptables: No chain/target/match by that name. - /sbin/iptables -t nat --append POSTROUTING -s 10.99.97.0/24 -j MASQUERADE
- /sbin/iptables --check FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
iptables: Bad rule (does a matching rule exist in that chain?). - /sbin/iptables --append FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
- /sbin/iptables --check FORWARD -s 10.99.97.0/24 -j ACCEPT
iptables: Bad rule (does a matching rule exist in that chain?). - /sbin/iptables --append FORWARD -s 10.99.97.0/24 -j ACCEPT
- /sbin/ip6tables -t nat --check POSTROUTING -s fd00::10:97:0/112 -j MASQUERADE
ip6tables: No chain/target/match by that name. - /sbin/ip6tables -t nat --append POSTROUTING -s fd00::10:97:0/112 -j MASQUERADE
- /sbin/ip6tables --check FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
ip6tables: Bad rule (does a matching rule exist in that chain?). - /sbin/ip6tables --append FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
- /sbin/ip6tables --check FORWARD -s fd00::10:97:0/112 -j ACCEPT
ip6tables: Bad rule (does a matching rule exist in that chain?). - /sbin/ip6tables --append FORWARD -s fd00::10:97:0/112 -j ACCEPT
- /sbin/iptables -t nat --check OUTPUT -s 10.99.97.0/16 -p udp --dport 53 -j DNAT --to 10.99.97.1:53
iptables: No chain/target/match by that name. - /sbin/iptables -t nat --append OUTPUT -s 10.99.97.0/16 -p udp --dport 53 -j DNAT --to 10.99.97.1:53
- /sbin/iptables -t nat --check OUTPUT -s 10.99.97.0/16 -p tcp --dport 53 -j DNAT --to 10.99.97.1:53
iptables: No chain/target/match by that name. - /sbin/iptables -t nat --append OUTPUT -s 10.99.97.0/16 -p tcp --dport 53 -j DNAT --to 10.99.97.1:53
- /sbin/ip6tables --wait -t nat --check OUTPUT -s fd00::10:97:0/112 -p udp --dport 53 -j DNAT --to fd00::10:97:1
ip6tables: No chain/target/match by that name. - /sbin/ip6tables --wait -t nat --append OUTPUT -s fd00::10:97:0/112 -p udp --dport 53 -j DNAT --to fd00::10:97:1
- /sbin/ip6tables --wait -t nat --check OUTPUT -s fd00::10:97:0/112 -p tcp --dport 53 -j DNAT --to fd00::10:97:1
ip6tables: No chain/target/match by that name. - /sbin/ip6tables --wait -t nat --append OUTPUT -s fd00::10:97:0/112 -p tcp --dport 53 -j DNAT --to fd00::10:97:1
- test -d /data/wireguard
- cat
++ cat /data/wireguard/server.private - cat /data/wireguard/peers/null.conf
- ip link show wg0
- ip link add wg0 type wireguard
Error: Unknown device type.
`
I can also share my docker-compose.yml file if someone thinks they can help.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels