NeoLoader Forum

try setting a password and test again,
i tested it locally and it works for me.

try using putty to connect with the telnet protocol to the port and teh server look if the connection will be opened

In any case a "nothing happen" response is not that helpful, an error message if possible should be added.

I allways connect by putty to server in ssh and I start Neoloader by ./Neoloader -core and I can see all log

I don't understand what you want tell me about telnet (connect to ip server:20035? I tried, but nothing in log and putty is black screen without anything)
I see just this error (if it is) in log Cannot connect to the D-Bus session bus, but the webUI work, from the remote UI I don't have any error message, just does not connect
I set password in NeoLoader.ini but is the same.
The pc with windows is in lan.
How I can test if port 20035 is open and listening?
Do you need that I post all configuration file?

try to connect from putty and start typing and press enter 1 or 2 times

observe the log of your neo on server if there was a conneciton you should get a log lien like

18:50:59: Recived Request form not logged in client

this would tell us that there is a connection established and that it fails later.

if that not happen than it means that there is a firewall or somethign in the way


we can also make a live team viever or VNC session to debug and hopefully resolve the issue

Hey David, could be the missing D-Bus the real connection problem? Theoretically D-Bus is needed for programs/processes to communicate with one another... (I presume NeoLoader uses QtDBus to communicate with the core)

no d-bus is only needed to prevent standby while neoloader is running.

DavidXanatos wrote:try to connect from putty and start typing and press enter 1 or 2 times

observe the log of your neo on server if there was a conneciton you should get a log lien like

18:50:59: Recived Request form not logged in client

this would tell us that there is a connection established and that it fails later.

if that not happen than it means that there is a firewall or somethign in the way


we can also make a live team viever or VNC session to debug and hopefully resolve the issue

Yes, I have this message:

If I can help you to understand my configuration:
I have ubuntu in virtual machine, and windows in real where running VM (I tried too with another pc in lan)
In VM I set the network adapter in "Bridged: Connected directly to the physical network".

If you want to try by team viever ok, we must organize for day and hour, by PM?

Thank you so much!

ok, i send you a pm.
not sure what fails are you sure the password is set the same on booth neos?

I set password "test" in the file NeoLoader.ini (/NeoLoader/Config/NeoLoader.ini => password)

Ok
solution

The value in "Local Name" must be set to empty in order for remote connections to work.

i will rework the connection video to avoid such trivial issues for the 0.50 final release.