installs
- h
high-magazine-39815
03/17/2022, 8:00 PMOk it's up, seems to have gotten certs - h
high-magazine-39815
03/17/2022, 8:01 PMdocker-compose up caddy Starting caddy ... done Attaching to caddy caddy | {"level":"info","ts":1647547193.9395163,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"} caddy | {"level":"warn","ts":1647547193.9406092,"msg":"input is not formatted with 'caddy fmt'","adapter":"caddyfile","file":"/etc/caddy/Caddyfile","line":1} caddy | {"level":"info","ts":1647547193.9429445,"logger":"admin","msg":"admin endpoint started","address":"tcp/localhost:2019","enforce_origin":false,"origins":["localhost:2019","[::1]:2019","127.0.0.1:2019"]} caddy | {"level":"info","ts":1647547193.943094,"logger":"http","msg":"server is listening only on the HTTPS port but has no TLS connection policies; adding one to enable TLS","server_name":"srv0","https_port":443} caddy | {"level":"info","ts":1647547193.9431052,"logger":"http","msg":"enabling automatic HTTP->HTTPS redirects","server_name":"srv0"} caddy | {"level":"info","ts":1647547193.9431973,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0xc0001f0e00"} caddy | {"level":"info","ts":1647547193.9434552,"logger":"tls","msg":"cleaning storage unit","description":"FileStorage:/data/caddy"} caddy | {"level":"info","ts":1647547193.944624,"logger":"tls","msg":"finished cleaning storage units"} caddy | {"level":"info","ts":1647547193.9454782,"logger":"http","msg":"enabling automatic TLS certificate management","domains":["dashboard.(redacted)"]} caddy | {"level":"info","ts":1647547193.9468641,"msg":"autosaved config (load with --resume flag)","file":"/config/caddy/autosave.json"} caddy | {"level":"info","ts":1647547193.9468863,"msg":"serving initial configuration"} - b
bored-island-21407
03/17/2022, 8:02 PMok, caddy shouldn't be the issue - h
high-magazine-39815
03/17/2022, 8:03 PMCaddyfile restored - h
high-magazine-39815
03/17/2022, 8:04 PMMy computer is definitely reaching out to the old server, I don't imagine that causing any issues though. - j
jolly-london-20127
03/17/2022, 8:05 PMyou're using your own domain i take it? - h
high-magazine-39815
03/17/2022, 8:05 PMone warning on starting:``` {"level":"warn","ts":1647547441.0483508,"msg":"input is not formatted with 'caddy fmt'","adapter":"caddyfile","file":"/etc/caddy/Caddyfile","line":2} ``` - b
bored-island-21407
03/17/2022, 8:05 PMthat is normal - h
high-magazine-39815
03/17/2022, 8:05 PMThese seem normal as well, probably:netmaker | [netmaker] 2022-03-17 20:04:01 no OAuth provider found or not configured, continuing without OAuth netmaker | [netmaker] 2022-03-17 20:04:01 could not set peers on network default : file does not exist netmaker | [netmaker] 2022-03-17 20:04:01 ERROR RETRIEVING EXTERNAL PEERS ON SERVER: could not find any records netmaker | [netmaker] 2022-03-17 20:04:01 could not set peers on network Qha3nzJs : file does not exist - b
bored-island-21407
03/17/2022, 8:06 PMthis is a fresh install? - h
high-magazine-39815
03/17/2022, 8:06 PMThen there's a logger error with a broken pipe and authorization, so that's my computer again. - h
high-magazine-39815
03/17/2022, 8:07 PMThe server install was fresh (when I reached out) but my local computer seems to still be running NetClient and is trying to reach the old server. - h
high-magazine-39815
03/17/2022, 8:07 PMOh, umm....the dashboard let me create the admin this time. - h
high-magazine-39815
03/17/2022, 8:08 PMThat was where I got stuck the last several times, I think we went on a rabbit trail, where maybe there was some sort of Caddy glitch/SSL issue, but it seems to have been resolved. - b
bored-island-21407
03/17/2022, 8:08 PMwere you bringing the containers up and down several times? - h
high-magazine-39815
03/17/2022, 8:08 PMthey're up in console, I'm going to restart them in daemon mode - b
bored-island-21407
03/17/2022, 8:09 PMcaddy runs into rate limits when you you restart it too quickly - b
bored-island-21407
03/17/2022, 8:09 PMand too often - h
high-magazine-39815
03/17/2022, 8:10 PMYeah, that didn't happen, the initial setup was several minutes apart - h
high-magazine-39815
03/17/2022, 8:10 PMWell that's....anticlimactic - h
high-magazine-39815
03/17/2022, 8:11 PMThanks for your help troubleshooting @User , I guess I get to play with Netmaker and see if I can break anything else now. Sorry for the rabbit trail that perhaps related to just restarting Caddy. (maybe?) - b
bored-island-21407
03/17/2022, 8:12 PMmaybe caddy, not sure.. just glad you are up and running - h
high-magazine-39815
03/17/2022, 8:13 PMSemi-related question, given my local computer is still reaching out to the old network, what's the cleanest way of killing that connection? I'm assuming that if I re-add it will at worst conflict, or likely just have two networks. - h
high-magazine-39815
03/17/2022, 8:13 PMwait, think I found it. /etc/netclient/netclient leave (should do the trick) - h
high-magazine-39815
03/17/2022, 8:15 PMHmm, Unauthorized. Network does not exist. But it does show up innetclient list - b
bored-island-21407
03/17/2022, 8:15 PMactually you probably want to do an netclient uninstall and download the updated binary that matches the sever - h
high-magazine-39815
03/17/2022, 8:15 PMProbably an artifact of me getting stuck and breaking netclient/wg a while ago. uninstall/reinstall sounds good - h
high-magazine-39815
03/17/2022, 8:16 PMThanks, I'll do that and report my success later. 👍 - h
high-magazine-39815
03/17/2022, 8:30 PMSomewhat related feedback: The Client Install section of access keys needs to mention that it needs to be run as root. This did not work. I tried prefixing it with sudo, or adding sudo before the sh, neither worked. It did seem to download netclient to my local dir, but somehow I got an older 0.9.4 (I think) version. Twice. - h
high-magazine-39815
03/17/2022, 8:31 PMI deleted and retried, as well as trying to use that (outdated) client to manually join, everything failed. Finally I (now as root) used the client install commands and it worked.