Advisory
[Update: 3-6-22 - 18:53 UTC]: The below advisory is no longer in affect. A hotfix has been added to the release which resolves the issue.
There is a bug with upgrading the netclient from 0.14.1 to 0.14.2. Please hold off on upgrades. the hotfix will be in the release shortly.
Here is the issue and recovery steps if you have already attempted an upgrade.
**Issue:**
netclient[59819]: [netclient] 2022-06-02 14:25:12 error publishing ping, mq setup error error: broker port is blank
Post "https:///api/nodes/adm/xxxx/authenticate": http: no Host in request URL
[netclient] 2022-06-02 20:14:17 register at https:///api/server/register
**Fix:**
1. open /etc/netclient/config/netconfig-<network> and add the api connection string to the "apihost" field, e.g. "api.domain.com:443"
2. Restart the daemon: systemctl restart netclient
Important Upgrade Notes:
- Default Compose File is now Traefik (docker-compose.traefik.yml)
- You can upgrade an existing Caddy-based installation to Traefik using the new docker-compose.traefik.yml
- You can also keep your existing Caddy-based installation/docker-compose and just change the image versions from 0.14.1 to 0.14.2
- If you do change to Traefik, you must wait a few minutes on clients to generate proper certs, as port changes to 443
What's new?
- Default proxy is now Traefik
- MQ public port is configurable and can run on 443 via Traefik
- Traefik removes port 80 and port 8883 dependencies
- Send server version to clients to detect if they are on the wrong version
- MQ address removed from access token
- added onfailure restart to Windows service
What's fixed?
- removed duplicate publishes from client
- minor fixes to peer logic
- failover for retrieving correct MQ address via API
- use interface as hostctl profile to avoid confilcts in DNS
- delete WireGuard interfaces on shutdown of docker netclient
Known Issues
- Windows Service: The old netclient Windows Service does not get uninstalled during upgrade. It also does not restart automatically on failure, which is absolutely necessary to function. If you're running an older Windows netclient, you must go to Windows Services, search for netclient, and change the settings so that it will "restart on failure"
- Problems with relay logic: if you update a relayed node's address, it will become un-relayed
- setting and unsetting the server as a relay will turn ON UDP HOLE PUNCHING + break network
- workaround: set udpholepunch off