Closed cryptomail2018 closed 5 years ago
Did you clean install 2.0.5. It's only an update. So you need 2.0.3 and then update it to 2.0.5.
Some web assets were missing in the build.
We are working on resolving this. For now follow Jack's advice.
thank you for info i try again with kind regards
Crypto Skimmerhttps://www.facebook.com/crypto.skimmer.1
On Sunday, 2 December 2018, 2:36:10 pm GMT+7, JackONeill12 <notifications@github.com> wrote:
Did you clean install 2.0.5. It's only an update. So you need 2.0.3 and then update it to 2.0.5.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
Some web assets were missing in the build.
We are working on resolving this. For now follow Jack's advice.
did exactly what you tell me to do fresh install of 2.0.3 setup all files run it first then shut down install 2.0.5 over it in upgrade . now i have error showing and blank screen with wheel spinning . see attached CMD error port is open on 5040 in security as well as 5040 is bot 4 in my instance.
This usually happens when you launch a second instance of the monitor without realizing there is already an instance running, hidden somewhere behind another window. ;)
not the case of this time , clean fresh install reboot and startup as per instruction 1 bot only
Well the error states that the port is already in use, so it doesn't seem like a PTM error. something about the way your VPS is configured perhaps?
yes i noticed that . port 5040 is purely for bot 4 PTM port is open in security settings , i try different port as well but no luck with kind regards
Crypto Skimmerhttps://www.facebook.com/crypto.skimmer.1
On Thursday, 6 December 2018, 3:28:18 pm GMT+7, HojouFotytu <notifications@github.com> wrote:
Well the error states that the port is already in use, so it doesn't seem like a PTM error. something about the way your VPS is configured perhaps?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
still have same problem with the monitor application GUI running