https://netmaker.org logo
Join Discord
Powered by
Trying to configure Netmaker with my
# install
b
Trying to configure Netmaker with my existing reverse-proxy (Nginx Proxy Manager). Hoping to avoid the full set of trial and error to figure this out. @glamorous-traffic-41474 did you end up with a working 
docker-compose.yml
you'd be willing to share? 🙂 Thanks!
b
you should be able to referance the Caddyfile and and put the entries there to to NPM equivalent .
b
Thank you, that looks like a better starting point than anything I was managing.
Think proxy's configured correctly, however 
dashboard.netmaker.mysubdomain.mydomain
is not communicating to backend. - ran quick install script - commented out Caddy from docker-compose - passed through ports in docker-compose
Copy code
netmaker-ui: 
.
.
  ports:
  - 80:80
and passed through port 8081 the same way for 
netmaker
itself ... * 
curl api.netmaker.mysubdomain.mydomain
from host returns 404 * 
curl api.netmaker.mysubdomain.mydomain
from 
netmaker-ui
container returns 301 Moved Permanently * 
curl 172.24.0.2:8081
from 
netmaker-ui
container returns 404 (
172.24.0.2
is internal Docker IP of netmaker container) * 
curl 192.168.1.117:8081
(LAN IP of netmaker host) - connection refused With verbosity set to 3 in docker-compose, I'm not seeing anything new in log. Any ideas appreciated!
b
how are you networking between your NPM and netmaker containers?
b
They are running on different hosts on a LAN. Netmaker install is in its own VM.
(Is there any way to increase logging other than 
VERBOSITY
in docker-compose? Surprised that at the maximum of 
VERBOSITY 3
, the logs on 
netmaker
are not returning any connection attempts ... 😖 )
b
netmaker ui should be logging all access request without verbosity set.
@bored-island-21407 how to get api request logs?
b
no easy way to get them
try curl api.netmaker.mysubdomain.mydomain/api/users/adm/hasadmin invalid endpoints will return a 404
3 Views
PreviousNext
Powered by