https://netmaker.org logo
Powered by
Do the ports just need to be forwarded on the linu...
# netmaker
f
Do the ports just need to be forwarded on the linux machine Cause it keeps erroring out for me
b
no... but just to be clear what machine are you talking about
f
The same one from the fedora thread, I have literally no idea what is wrong with it
b
the netmaker server?
f
Yep
b
what errors are you talking about
check you firewall settings; you are not permitting http and https traffic
f
Same thing happens
b
Take a look at the caddy logs and see what the errors are
f
Where would the logs be ?
Could you tell me where to find the logs so I can post them ?
b
docker logs caddy
f
These are the logs
b
did you read them? you have a firewall problem {"level":"error","ts":1675536992.8882284,"logger":"http.acme_client","msg":"challenge failed","identifier":"broker.nm.86-122-99-41.nip.io","challenge_type":"http-01","problem":{"type":"urn:ietf:params:acme:error:connection","title":"","detail":"86.122.99.41: Fetching http://broker.nm.86-122-99-41.nip.io/.well-known/acme-challenge/CIlkW-Ys7fC358CCdpWhFue0DObzjWimSNrpZtmveD8: Timeout during connect (likely firewall problem)","instance":"","subproblems":[]}}
what do the caddy logs show?
f
Those are the logs for caddy though
b
sorry my bad.
you need to fix your firewall; the letsencrypt challenge over http are timing out
f
And what exactly do I need to fix in the firewall ? It's a fresh install of Fedora, so idk the problem is
b
where is the machine... if it is a vps there maybe a cloud firewall as well
f
It's a local computer
b
does your ISP have a firewall that blocks port 80 and 443... a lot do
is your local computer behind a router?
f
Yes
b
if so, then you have to port forward on the router
it is recommended that the netmaker server be run on a machine with a public ip address --- -not behind NAT
f
Is there some performance loss or anything like that ?
b
depends on your ISP
it is easy to get one the cheapest vps from a cloud provider (eg. DigitalOcean, Linode, AWS, GCP, etc). Netmaker will run on most of the cheapest offerings so it would only cost ~5$ per month
f
I love it when nothing changes
And don't think I did anything wrong in the networking part ?
The only other thing that I legit don't know if it will help is to put the IP as static
@bored-island-21407 Well, managed to somewhat get further, but errr, now I have ANOTHER issue [netmaker] 2023-02-05 11:55:31 connecting to sqlite [netmaker] 2023-02-05 11:55:31 database successfully connected [netmaker] 2023-02-05 11:55:31 no OAuth provider found or not configured, continuing without OAuth [netmaker] 2023-02-05 11:55:31 error setting iptables forward policy: exit status 3
Server ID: /root/nm-quick-interactive.sh: line 378: [: ==: unary operator expected server node not yet configured, retrying... waiting for server node to become available Setup also appears to get stuck on this
@bored-island-21407 quick update: managed to get it working by disabling dns mode, but err, I can't seem to get to my other services like my router gateway or my portainer instance
Could you help me with that ?
b
Don't use your netmaker server as a gateway. If you really need a gateway, install netclient
f
So what do I do ?
@bored-island-21407 What do I even do in this scenario ?
b
Go into the netmaker ui and select the netmaker node and disable ingress egress and relay if enabled. Install netclient and join the network. Use the new node for your gateways.
f
@bored-island-21407 Yeah, that, errr, that isn't gonna work
Do you have any other ideas ?
Since the server outright dies due to iprules
Or something like that
So, errr, what do I do ?
b
in docker-compose change MANAGE_IPTABLES to "off" and PORT_FORWARD_SERVICES to ""
5 Views
PreviousNext
Powered by