@wint0178 on the other post, I see you were able to see the nodes. Still do you see this issue?

@wint0178 Are you using MySensors library?
Your MQTT broker should be accessible to all of your hardware gateway nodes and MyController server. MyController server is acting as MQTT client, just like another MQTT device in your network.

@wint0178 You can use letsencrypt certification setup with https_acme to your DDNS setup, https://v2.mycontroller.org/docs/installation/advanced-installation/backend-configuration/

@jkandasa I have fixed this. available in the docker container(2.1.0-devel). yet to update in executable.

@wint0178 I have not experienced this kind of issue. check the filesystem. you can find the root cause. Please let us know your findings. You can check this after your family road trip

@wint0178 No, keep default labels. as @JeeLet mentioned can you check any other service is consuming the serial port? Do you see any error on the gateway?

@JeeLet @wint0178 Yes, this known issue. but it will not impact the functionality. I will fix this soon.

@wint0178 we have many options, one of them is, port forward required services as you mentioned in your router. you need separate entry for each service(MyController, MQTT broker, etc.,)

Some use reverse proxy. do one a port forward to your reverse proxy via 443 and 80, then do all other changes in your reverse proxy. Someof the famous reverse proxy servers are caddyserver, traefik, nginx, etc.,

@wint0178 said in Moving Server to another location:

As for the dashboard, there is nothing there. In v1.5 there was a clock and location, but not in v2.0. Is here a way to add those back?

No, for now in V2 we do not have clock and location.

@wint0178 what is the labels do you use in mycontroller.yaml under gateway? you have to use that label in your gateway settings label section.