You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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!
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.
The text was updated successfully, but these errors were encountered: