[Feature Request]: How to use cloud server as master and local as worker？

[wonb168]

Is there an existing feature request for this?

• I have searched the existing issues

What is your feature request?

I need to use a cloud server to centrally manage machines across different internal networks. The internal machines can access the cloud server, but not the other way around. How should I configure this?

I tried installing and running Cronicle on both the cloud server and an internal machine, but I can't see the internal machine in the web management interface.

My version is 0.9.90

Code of Conduct

• I agree to follow this project's Code of Conduct

[peterbuga]

@wonb168

I have the exact setup as you mention. something to start with bluet/docker-cronicle-docker#37 (comment)

ps: short-er answer you need some vpn+dns combo for master to access the worker nodes otherwise won't work as expected (AFAIK)

[jhuckaby]

Yeah, both servers need to be on the same "network" (LAN) in order to be visible to each other. Cronicle v1 opens connections in both directions, hence this requirement. Cronicle v2 (coming out later this year) is totally redesigned to ONLY open connections from workers to the master server, making this setup much easier.

For your current situation and Cronicle v1, I highly recommend Tailscale. It's free and does the needful.

[wonb168]

v2 like cronsun? support only workers can connect master?

[jhuckaby]

I've never heard of cronsun before. Cronicle v2 is redesigned to support more complex architectures, in that there is no longer the requirement for bidirectional network connections between master and worker (like it is now). The new design only connects one way (worker to master) making it much easier to install workers behind firewalls, or in a different network / cloud than the master, and they can also run with no open ports (no incoming connections), etc.