<![CDATA[MangoESV3 refused to connect after upgrade 3.34]]>Hi Support,

After upgrade to 3.3.4, the mangoES refused to connect. This error page "This site cant be reached" after restart. This is the first attempt to do upgrade as it is a new purchased unit.

I have tried the IP address in the URL and do a restart again but no success. What could be wrong during the upgrade process?

Any suggestion or help is appreciated.
Thank you in advanced

]]>https://forum.mango-os.com/topic/3418/mangoesv3-refused-to-connect-after-upgrade-3-34RSS for NodeMon, 20 Jul 2026 10:41:03 GMTMon, 16 Apr 2018 11:19:22 GMT60<![CDATA[Reply to MangoESV3 refused to connect after upgrade 3.34 on Wed, 06 Jun 2018 14:29:43 GMT]]>Upon investigation, I found Mango online and accessible. I updated it from 3.4.1 to 3.4.3

]]>https://forum.mango-os.com/post/18742https://forum.mango-os.com/post/18742Wed, 06 Jun 2018 14:29:43 GMT<![CDATA[Reply to MangoESV3 refused to connect after upgrade 3.34 on Wed, 30 May 2018 04:54:39 GMT]]>@phildunlap
After several unsuccessful attempts, may I request that Mango to investigate into the root cause? I am willing to send you the details to access into the web server remotely.

My main concern is that I do not wish to make it worse by doing something wrongly to the system or if other errors occurred, it is difficult to isolate the problem. Besides, I am under pressure to start setting up of this MangoES unit for a demo presentation.

Let me know your comments.

Thanks

]]>https://forum.mango-os.com/post/18661https://forum.mango-os.com/post/18661Wed, 30 May 2018 04:54:39 GMT<![CDATA[Reply to MangoESV3 refused to connect after upgrade 3.34 on Mon, 21 May 2018 15:03:56 GMT]]>Hmm. It sounds like one or more modules has a module.properties file that is most likely 0 bytes long. I saw this on someone's system after an update. Perhaps try removing all your modules, and then using the /modules.shtm page to install the modules you need.

]]>https://forum.mango-os.com/post/18521https://forum.mango-os.com/post/18521Mon, 21 May 2018 15:03:56 GMT<![CDATA[Reply to MangoESV3 refused to connect after upgrade 3.34 on Mon, 21 May 2018 07:55:29 GMT]]>@phildunlap
I have followed your instruction steps to perform the upload enterprise bundle and restart but it does not resolve the startup issue.

part of console screen terminal:
[mango@mangoES3508 ~]# cd /opt/mango/bin; ./ma.sh start
MA_HOME is /opt/mango
Archive: /opt/mango/m2m2-core-3.4.4.zip
........
Total output of 1.03 MB was truncated at 97.66 kB.
[mango@mangoES3508 bin]# cd /opt/mango/bin; ./ma.sh start
MA_HOME is /opt/mango
MA already running with Process ID: 1015
ma-start: MA done

Below is the console screen terminal for the java version :

[mango@mangoES3508 bin]# cd /opt/mango/bin; ./ma.sh start
MA_HOME is /opt/mango
MA already running with Process ID: 1015
ma-start: MA done
[mango@mangoES3508 bin]# java -version
java version "1.8.0_131"
Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
Java HotSpot(TM) Client VM (build 25.131-b11, mixed mode)
[mango@mangoES3508 bin]#

Pls note that I have been troubled with this issue since the purchased on the feb2018. Currently I am using trial version to do the application development.
I need your support to look into it as I am about to due for a presentation with the new MangoES.

Thank you in advance.

]]>https://forum.mango-os.com/post/18519https://forum.mango-os.com/post/18519Mon, 21 May 2018 07:55:29 GMT<![CDATA[Reply to MangoESV3 refused to connect after upgrade 3.34 on Tue, 24 Apr 2018 17:00:50 GMT]]>Something is amiss. Did you update / install Java?

I would try downloading the enterprise bundle of 3.3.4 from https://store.infiniteautomation.com/core, renaming it to m2m2-core-3.3.4.zip, place it in /opt/mango/ and attempt to start it again. This will let the scripts perform the upgrade and ensure there are no duplicate jars.

]]>https://forum.mango-os.com/post/18150https://forum.mango-os.com/post/18150Tue, 24 Apr 2018 17:00:50 GMT<![CDATA[Reply to MangoESV3 refused to connect after upgrade 3.34 on Tue, 24 Apr 2018 03:46:54 GMT]]>@phildunlap

I have removed the advancedComponents module as per your comment. Then I run ma-start command or url://IP address, it does not launch the login page in chrome as per expected.

Below i have attached the ma and ma-script file for your action.

[shareable link](https://drive.google.com/file/d/12T4HlRaWmeiX5cFB7JBxGrYm47GODaiu/view?usp=sharing
https://drive.google.com/file/d/166ladCzcLizSWdM57FTOBXjA37mF2dhF/view?usp=sharing)

Hope you can look into it and give me guidance to resolve it.

Thank you in advance.

]]>https://forum.mango-os.com/post/18142https://forum.mango-os.com/post/18142Tue, 24 Apr 2018 03:46:54 GMT<![CDATA[Reply to MangoESV3 refused to connect after upgrade 3.34 on Mon, 23 Apr 2018 14:08:09 GMT]]>Hi Desmond,

It looks like something is wrong in the advanced components module that you have installed. Consider removing it,

rm -r /opt/mango/web/modules/advancedComponents

And trying to start again. You can reinstall it on the module page.

]]>https://forum.mango-os.com/post/18121https://forum.mango-os.com/post/18121Mon, 23 Apr 2018 14:08:09 GMT<![CDATA[Reply to MangoESV3 refused to connect after upgrade 3.34 on Mon, 23 Apr 2018 07:22:45 GMT]]>@phildunlap
I have managed to see the directory of mango now. For your information running the command cd /opt/mango/bin; ./ma.sh start give the result as per photo.
0_1524467011328_error1.jpg

I tried to login locally via the url give the result as per photo.
0_1524467450565_error2.jpg.
The IP address 192.168.1.12 response with the ping command and I can login the wed server.

This is the new purchased unit on feb2018 and I have not done nothing else other than upgrading the web admin and mangoES. It used to be login without issue before upgrade.

Pls help as I am not familiar with administering the web server. I cant figure out what need to be done.

Thank you in advance.

]]>https://forum.mango-os.com/post/18120https://forum.mango-os.com/post/18120Mon, 23 Apr 2018 07:22:45 GMT<![CDATA[Reply to MangoESV3 refused to connect after upgrade 3.34 on Mon, 16 Apr 2018 15:46:55 GMT]]>Might you have manually upgraded it and done some step as the root user, while ls -l /opt/mango reveals files owned by 'mango'? Fix by chown -R mango:mango /opt/mango

Have you tried to see what happens if you attempt to launch Mango at the command line with

cd /opt/mango/bin; ./ma.sh start

?

]]>https://forum.mango-os.com/post/18035https://forum.mango-os.com/post/18035Mon, 16 Apr 2018 15:46:55 GMT