@kirill-kostin Thank you for letting us know, I've fixed the issue on our end.

@vishalcapri Hi there,

Apologies for the issues here, but I fixed this issue yesterday or the day before. I did something incorrectly with the renewal process, and it caused this strange behavior. Can you try again and let me know if it's fixed for you?

Liv

@kirill-kostin Thank you for letting us know, I've fixed the issue on our end.

@hayden_AUS said in mango.properties file syntax:

Whereas the "Clean" mango.properties file in the Mango Docs doesn't even have hashtags for comments:

The port at which Mango Automation will listen for browser connections
web.port=8080
The host interface to which Mango Automation will bind and listen for new connections
0.0.0.0 is the special interface that will force a bind to all available interfaces
web.host=0.0.0.0

Can you point me to what page this is in the documentation? This is something I want to fix to prevent confusion to future users of the docs.

Liv

@BG
Brian,

No worries at all, glad to help out. I look forward to seeing the solution.

@BG
Brian,

I've found that the documentation for v3 mentions Java 8, but has some very outdated links to recommendations for builds. For Mango versions 4 and 5, we recommend using Azul Zulu, so in this case I would recommend Azul Zulu JDK 8, which you can find here (I filled in the Java version, OS, and architecture for you): https://www.azul.com/downloads/?version=java-8-lts&os=rhel&architecture=x86-64-bit&package=jdk#zulu

I would recommend installing via RPM, instead of dropping a ZIP somewhere. Then, remove Java 21 to reduce confusion and the possibility that Mango still picks up 21.

Also, a heads up. We don't test with or support MariaDB, so I'm unsure if you could run into issues there. If it was working just fine for you before, then I'm sure it'll continue to work, but just letting you know.

Liv
Radix IoT

BG,

I've looked into the code on our end, and while I can't say for sure what is happening - I'm expecting that it may have something to do with your environment. We use some code to determine a unique machine identifier for licensing purposes, and the most likely issue seems like it's failing to either read or write to the HOME/.ma file.

What distribution and version of Linux were you using before? Also, how does Plesk play into this? Is MySQL hosted on your system, or is it a shared database cluster? When I used web hosts in the past with a control panel, sometimes they did some weird things with permissions. Or, it could potentially just be an incompatibility with Alma Linux 9. We have tested later versions with Alma, but I can't say I've tried Mango 3 with it. If I get a chance later, I'll try tossing Mango 3 onto a quick Alma Linux 9 container and seeing if I get an issue myself.

Liv
Radix IoT