MX Interface problem

[griffo42]

This occurred when I keyed in the usual "localhost:8998" address. Any advice?

Screenshot 2023-06-10 072919.png

Keith

[Mapantz]

Are you trying to access it from the same machine, or a different one?

[griffo42]

Same machine.

Keith

[freddie]

There is no authentication done in MX, so you won't get a 401 http response from MX. Is MX actually running? If it is then could you please zip up the latest log file from the MXdiags folder in your installation and attach it to a reply to this topic?

It is my suspicion that MX may not be running, and something else is using port 8998.

[griffo42]

I disabled FTP logging as per this advice:

This was picked up in another thread. Please disable FTP logging for now.

If you need FTP logging, then disabling it, and re-enabling should fix the immediate problem - but see above for restarting CMX.

The error occurs if FTP logging is already enabled when CMX starts; if you enable FTP logging whilst CMX is running it will log correctly until CMX is restarted, so please disable it before restarting.

In response to yours:

There is no authentication done in MX, so you won't get a 401 http response from MX. Is MX actually running? If it is then could you please zip up the latest log file from the MXdiags folder in your installation and attach it to a reply to this topic?

It is my suspicion that MX may not be running, and something else is using port 8998.

MX is running and updating my website/s.

Screenshot 2023-06-10 100721.png

I found these log files in my MXDiags folder. I notice that there are errors reported in the larger file.

Keith

[griffo42]

Further to my previous post, the ai version of theCMX Interface Dashboard etc. by Neil Thomas works perfectly.

[mcrossley]

Neils interface uses the same calls into MX as the standard interface. Does the standard interface work in an "Incognito" browser window?