Trouble with updating Procon

[Wurmfutter]

Hello there.

 

I just downloaded procon from the download section here, and it seems like it's still trying to contact repo.myrcon.COM for updates.

I tried to work around this by pointing to the myrcon.net IP via HOSTS file, but to no avail.

 

What am I doing wrong? I can't connect to my server without an update, apparently.

[Prophet731]

It shouldn't be checking for updates because that should be the most updated client.

 

@ColColonCleaner are you able to rebuild procon to avoid the checks for updates in the base program or we could update it to check for a new version at myrcon.net instead if for some reason an old bug now shows up.

 

Sent from my ONEPLUS A5010 using Tapatalk

[Wurmfutter]

It shouldn't be checking for updates because that should be the most updated client.

I agree, it shouldn't, since even my server provider recommends the current 1.5.1.1 - but to the best of my knowledge it does. It also offers me to send usage statistics to the old .COM site in the initial setup.

[Wurmfutter]

I'm experiencing high levels of weirdness here.

 

I gave it a shot and simply downloaded all files from my servers procon layer to overwrite my local procon. Once I do that, I'm in a weird state of half-connect - I can see the current player count and my servers name on procons homepage, however when I want to access anything else it reports incorrect user/password. Additionally, I noticed that the config I downloaded from the procon layer uses another port (47200 instead of 13041 like the setup instructions from my server provider says).

 

If I only overwrite everything BUT the/config folder I'm back to the state of "trying to connect" while my procon client displays the following error message in the bottom (after reverting my modifications to the hosts-file):

 

"Error downloading update: the remote name could not be resolved 'repo.myrcon.com' (translated from german error message).

 

https://i.imgur.com/AcNWczg.png

[Timm]

@Wurmfutter just turn off update check on both your Procon layer on host and client

https://prnt.sc/osvx9y

also you can disable udpate via FTP on you Layer

go to Configs\procon.cfg and set to FALSE http://prntscr.com/osvygz by default they are TRUE

 

 

@Prophet731 you can set to false update check and distribute with the update disabled download version on you webstie.

[Prophet731]

@Wurmfutter just turn off update check on both your Procon layer on host and client

https://prnt.sc/osvx9y

also you can disable udpate via FTP on you Layer

go to Configs\procon.cfg and set to FALSE http://prntscr.com/osvygz by default they are TRUE

 

 

@Prophet731 you can set to false update check and distribute with the update disabled download version on you webstie.

 

Colon was going to release a new procon version that supports the latest .NET framework. So makes sense to just do it then. 

[Timm]

Also please attempt to https://myrcon.net/topic/378-old-bf4def-you-distribute/?do=findComment&comment=52972

[Wurmfutter]

SOLVED.

 

I opened a ticket with my server provider and they did "something", I'm now able to connect using 1.5.1.1. Seems like the issue was on their side.