jhuckaby
Change port for a slave
I was able to hack pixl-server-web to listen on a specific IP, and was thus able to start the Slave as intended. I then encountered that the "add server" feature does not allow anything but an IP or a Hostname, leaving me unable to specify a port, and eventually all adds failed since the server wasn't listening.
Through the logs, I found that the reason it couldn't connect was that it tried port 80 for the slave (I run the master on port 80).
Could it be a thing to be able to specify "host:port", or even "scheme://host.port" in Add server? (I imagine some might want to use TLS for their master/slave setups.
Hello, and thanks for the issue report. I don't know of any current solution to this issue. But in a future release I can make the server-to-server communication available on a different port than the main web interface. I will add this to this TODO list. Thanks!
Hi, hope this is still in consideration. This is needed also if there is a load balancer preventing direct traffic to the workers, so I'm able to map different ports on same host to different workers.
Hi there! So sorry for the 7-year delay on this. I have not forgotten! Cronicle v2 has a completely redesigned server-to-server communication system, where the worker nodes now connect to the master server (and not the other way around). This design allows for much easier installations in complex architectures, as the only server with a socket listener is the master server, and all connections are one-way.
Cronicle v2 will be released later this year (2025).