Jump to content
Prophet731

Procon Version 1.5.3.0

Recommended Posts

This release has been upgraded to the .NET Framework 4.7. You will need to have that version installed in order to run all versions past 1.5.3.0. This will be released next week on Friday (11/22/19). If you are already running version 1.5.2.1 then it should prompt you for this update. Follow this topic to be notified when it's released if you haven't upgraded yet to 1.5.2.1

 

Changes

  • Compiled for .NET Framework 4.7
  • Added missing BFHL definitions

 

Docker Support

 

Also in this version I will hopefully have a docker version available for procon. This is for the more advanced users but I think it would be worth it. This is also my first attempt at building a docker image so expect problems with my noobness. :D

 

You can try out the docker stuff here https://github.com/AdKats/Procon1Docker Needs more documentation but it's there.

 

 

Download

 

https://myrcon.net/topic/2-procon-1x/

Edited by Prophet731
Added link to download newest version

The developer of the Battlefield Admin Control Panel (BFACP)

For BFACP support please post in the BFACP topic linked above.

Do not contact me via PM on the forums for help with procon. Please make a topic for it. Only PM's I will accept will revolve around any website issues.

Air VPN - The air to breathe the real Internet

Share this post


Link to post

What benefits will this version get? Better optimization or?

Or is it a release, just not to use the old version of .NET and just optimized to .NET 4.7?

Share this post


Link to post

4.x version was supposed to be released years ago but it never did. We're just releasing a 4.7 version so it uses the latest version dotnet framework. It was mostly issues with windows 10 not having 3.5 installed. Besides doesn't hurt to be up-to-date. Hopefully all goes well because plugins are not tested with this framework.


The developer of the Battlefield Admin Control Panel (BFACP)

For BFACP support please post in the BFACP topic linked above.

Do not contact me via PM on the forums for help with procon. Please make a topic for it. Only PM's I will accept will revolve around any website issues.

Air VPN - The air to breathe the real Internet

Share this post


Link to post

I have a few suggestions for the docker version
  

 
Do not run procon as root (it is good practise to run applications with an user that does not exist on the host system). This ensures that software that manages to escape the container is not automatically root on the docker host. 

ARG UID=5000
ARG GID=5000

# account for execution
RUN groupadd -r -g $GID procon && \
    useradd -r -g procon -u $UID procon && \
    chown procon:procon -R /procon

# switch user
USER procon:procon

 
Your setup does not allow updates of the container. I would use volumes for the config and plugins, because those folders should be persistent over updates. Otherwise you will lose changes between container updates.

VOLUME ["/procon/Configs", "/procon/Plugins"]

ADD Configs
ADD Plugins
add both folders to the container, but changes are only saved within the container. So changes to plugin settings will be lost.

 

An option would be:

  1. rm Configs && Plugins within the Docker image/Dockerfile
  2. mount ./Configs to /procon/Configs
  3. mount ./Plugins to /procon/Plugins

It would be possibly to mount the volumes so:

  • docker run: -v localPath:RemotePath
  • docker-compose:
    • volumes:
       - ./Configs:/procon/Configs
       - ./Plugins:/procon/Plugins
      

 
Here is an example how I use procon in docker: (P.S.: The procon.zip is stored locally, because well myrcon was down in the past). I use docker volumes. The data is then located at /var/lib/docker/volumes/name/_data/

 
DockerFile:

# Docker PRoCon Image
# Creator:  H3dius/Hedius [email protected]
FROM mono:latest

# user and group ID of the account for full read/write access
ARG UID=10000
ARG GID=10000
ARG FILE="procon_1.5.1.1.zip"

LABEL maintainer="Hedius @ gitlab.com/hedius" \
      description="PRoCon Docker image" \
      version="1.0"

# install unzip
RUN apt-get update && apt-get install -y unzip

# account for execution
RUN groupadd -r -g $GID procon && \
    useradd -r -g procon -u $UID procon

#Set the workdirectory
WORKDIR /opt/procon

ADD --chown=procon:procon $FILE .

RUN unzip $FILE && \
    chown procon:procon -R /opt/procon && \
    rm -r Configs Plugins $FILE

USER  procon:procon

VOLUME ["/opt/procon/Configs", "/opt/procon/Plugins"]

ENTRYPOINT ["mono", "PRoCon.Console.exe"]

docker-compose.yml

version: '2.4'
services:
  procon1:
    container_name: procon1
    build:
      context: .
    image: hedius/procon:1.0
    restart: unless-stopped
    ports:
      - "13001:13000"
    volumes:
      - type: volume
        source: config1
        target: /opt/procon/Configs
      - type: volume
        source: plugin1
        target: /opt/procon/Plugins
      - type: volume
        source: log1
        target: /opt/procon/Logs
    security_opt:
      - no-new-privileges
    tty: true
    mem_limit: 3G
    mem_reservation: 2500M

volumes:
  config1:
  plugin1: 
  log1:


Share this post


Link to post

 

I have a few suggestions for the docker version

  

 

Do not run procon as root (it is good practise to run applications with an user that does not exist on the host system). This ensures that software that manages to escape the container is not automatically root on the docker host. 

ARG UID=5000
ARG GID=5000

# account for execution
RUN groupadd -r -g $GID procon && \
    useradd -r -g procon -u $UID procon && \
    chown procon:procon -R /procon

# switch user
USER procon:procon

 

Your setup does not allow updates of the container. I would use volumes for the config and plugins, because those folders should be persistent over updates. Otherwise you will lose changes between container updates.

VOLUME ["/procon/Configs", "/procon/Plugins"]

ADD Configs

ADD Plugins

add both folders to the container, but changes are only saved within the container. So changes to plugin settings will be lost.

 

An option would be:

  1. rm Configs && Plugins within the Docker image/Dockerfile
  2. mount ./Configs to /procon/Configs
  3. mount ./Plugins to /procon/Plugins

It would be possibly to mount the volumes so:

  • docker run: -v localPath:RemotePath
  • docker-compose:
    • volumes:
       - ./Configs:/procon/Configs
       - ./Plugins:/procon/Plugins
      

 

Here is an example how I use procon in docker: (P.S.: The procon.zip is stored locally, because well myrcon was down in the past). I use docker volumes. The data is then located at /var/lib/docker/volumes/name/_data/

 

DockerFile:

# Docker PRoCon Image
# Creator:  H3dius/Hedius [email protected]
FROM mono:latest

# user and group ID of the account for full read/write access
ARG UID=10000
ARG GID=10000
ARG FILE="procon_1.5.1.1.zip"

LABEL maintainer="Hedius @ gitlab.com/hedius" \
      description="PRoCon Docker image" \
      version="1.0"

# install unzip
RUN apt-get update && apt-get install -y unzip

# account for execution
RUN groupadd -r -g $GID procon && \
    useradd -r -g procon -u $UID procon

#Set the workdirectory
WORKDIR /opt/procon

ADD --chown=procon:procon $FILE .

RUN unzip $FILE && \
    chown procon:procon -R /opt/procon && \
    rm -r Configs Plugins $FILE

USER  procon:procon

VOLUME ["/opt/procon/Configs", "/opt/procon/Plugins"]

ENTRYPOINT ["mono", "PRoCon.Console.exe"]

docker-compose.yml

version: '2.4'
services:
  procon1:
    container_name: procon1
    build:
      context: .
    image: hedius/procon:1.0
    restart: unless-stopped
    ports:
      - "13001:13000"
    volumes:
      - type: volume
        source: config1
        target: /opt/procon/Configs
      - type: volume
        source: plugin1
        target: /opt/procon/Plugins
      - type: volume
        source: log1
        target: /opt/procon/Logs
    security_opt:
      - no-new-privileges
    tty: true
    mem_limit: 3G
    mem_reservation: 2500M

volumes:
  config1:
  plugin1: 
  log1:


 

Made some of this changes in the develop branch.


The developer of the Battlefield Admin Control Panel (BFACP)

For BFACP support please post in the BFACP topic linked above.

Do not contact me via PM on the forums for help with procon. Please make a topic for it. Only PM's I will accept will revolve around any website issues.

Air VPN - The air to breathe the real Internet

Share this post


Link to post

Only issue I ran into was trying to update from the older one, threw up an error about using a newer version (assuming .net framework) Other than that everything seems to be running great, thanks again.

Share this post


Link to post

It threw up an error about needing. Net 4.7?

 

Sent from my ONEPLUS A5010 using Tapatalk


The developer of the Battlefield Admin Control Panel (BFACP)

For BFACP support please post in the BFACP topic linked above.

Do not contact me via PM on the forums for help with procon. Please make a topic for it. Only PM's I will accept will revolve around any website issues.

Air VPN - The air to breathe the real Internet

Share this post


Link to post

It downloaded the update, asked to restart to install, then this popped up. Same error on 2 machines.

 

error.png

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.BadImageFormatException: Could not load file or assembly 'C:\Users\Stov3top\Desktop\Procon 1.5.2.1\Updates\PRoConUpdater.exe' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.
File name: 'C:\Users\Stov3top\Desktop\Procon 1.5.2.1\Updates\PRoConUpdater.exe'
   at System.Reflection.AssemblyName.nGetFileInformation(String s)
   at System.Reflection.AssemblyName.GetAssemblyName(String assemblyFile)
   at PRoCon.Core.AutoUpdates.AutoUpdater.BeginUpdateProcess(PRoConApplication praApplication) in C:\Users\andre\Source\Repos\AdKats\Procon-1\src\PRoCon.Core\AutoUpdates\AutoUpdater.cs:line 406
   at PRoCon.Forms.frmMain.toolStripDownloading_Click(Object sender, EventArgs e) in C:\Users\andre\Source\Repos\AdKats\Procon-1\src\PRoCon\Forms\frmMain.cs:line 562
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.StatusStrip.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].



************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.9043 (WinRelRS5.050727-9000)

----------------------------------------
PRoCon
    Assembly Version: 1.5.2.1
    Win32 Version: 1.5.2.1

----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.9038 (WinRelRS5.050727-9000)

----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.9042 (WinRelRS5.050727-9000)

----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.9031 (WinRelRS5.050727-9000)

----------------------------------------
PRoCon.Core
    Assembly Version: 1.5.2.1
    Win32 Version: 1.5.2.1

----------------------------------------
System.Core
    Assembly Version: 3.5.0.0
    Win32 Version: 3.5.30729.9034 built by: WinRelRS5

----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.9031 (WinRelRS5.050727-9000)

----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.9031 (WinRelRS5.050727-9000)

----------------------------------------
PRoConPluginEnumAssembly
    Assembly Version: 0.0.0.0
    Win32 Version: 1.5.2.1

----------------------------------------
PRoConPluginEnumAssembly
    Assembly Version: 0.0.0.0
    Win32 Version: 1.5.2.1

----------------------------------------
PRoConPluginEnumAssembly
    Assembly Version: 0.0.0.0
    Win32 Version: 1.5.2.1

----------------------------------------
PRoConPluginEnumAssembly
    Assembly Version: 0.0.0.0
    Win32 Version: 1.5.2.1

----------------------------------------
PRoConPluginEnumAssembly
    Assembly Version: 0.0.0.0
    Win32 Version: 1.5.2.1

----------------------------------------
PRoConPluginEnumAssembly
    Assembly Version: 0.0.0.0
    Win32 Version: 1.5.2.1

----------------------------------------
PRoConPluginEnumAssembly
    Assembly Version: 0.0.0.0
    Win32 Version: 1.5.2.1

----------------------------------------
PRoConPluginEnumAssembly
    Assembly Version: 0.0.0.0
    Win32 Version: 1.5.2.1

----------------------------------------
Accessibility
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.9031 (WinRelRS5.050727-9000)

----------------------------------------
System.Web
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.9031 (WinRelRS5.050727-9000)

----------------------------------------
System.Design
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.9038 (WinRelRS5.050727-9000)

----------------------------------------
Ionic.Zip.Reduced
    Assembly Version: 1.9.1.5
    Win32 Version: 1.9.1.5

----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Edited by Stov3top

Share this post


Link to post

 

It downloaded the update, asked to restart to install, then this popped up. Same error on 2 machines.

 

error.png

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.BadImageFormatException: Could not load file or assembly 'C:\Users\Stov3top\Desktop\Procon 1.5.2.1\Updates\PRoConUpdater.exe' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.
File name: 'C:\Users\Stov3top\Desktop\Procon 1.5.2.1\Updates\PRoConUpdater.exe'
   at System.Reflection.AssemblyName.nGetFileInformation(String s)
   at System.Reflection.AssemblyName.GetAssemblyName(String assemblyFile)
   at PRoCon.Core.AutoUpdates.AutoUpdater.BeginUpdateProcess(PRoConApplication praApplication) in C:\Users\andre\Source\Repos\AdKats\Procon-1\src\PRoCon.Core\AutoUpdates\AutoUpdater.cs:line 406
   at PRoCon.Forms.frmMain.toolStripDownloading_Click(Object sender, EventArgs e) in C:\Users\andre\Source\Repos\AdKats\Procon-1\src\PRoCon\Forms\frmMain.cs:line 562
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.StatusStrip.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].



************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.9043 (WinRelRS5.050727-9000)

----------------------------------------
PRoCon
    Assembly Version: 1.5.2.1
    Win32 Version: 1.5.2.1

----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.9038 (WinRelRS5.050727-9000)

----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.9042 (WinRelRS5.050727-9000)

----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.9031 (WinRelRS5.050727-9000)

----------------------------------------
PRoCon.Core
    Assembly Version: 1.5.2.1
    Win32 Version: 1.5.2.1

----------------------------------------
System.Core
    Assembly Version: 3.5.0.0
    Win32 Version: 3.5.30729.9034 built by: WinRelRS5

----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.9031 (WinRelRS5.050727-9000)

----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.9031 (WinRelRS5.050727-9000)

----------------------------------------
PRoConPluginEnumAssembly
    Assembly Version: 0.0.0.0
    Win32 Version: 1.5.2.1

----------------------------------------
PRoConPluginEnumAssembly
    Assembly Version: 0.0.0.0
    Win32 Version: 1.5.2.1

----------------------------------------
PRoConPluginEnumAssembly
    Assembly Version: 0.0.0.0
    Win32 Version: 1.5.2.1

----------------------------------------
PRoConPluginEnumAssembly
    Assembly Version: 0.0.0.0
    Win32 Version: 1.5.2.1

----------------------------------------
PRoConPluginEnumAssembly
    Assembly Version: 0.0.0.0
    Win32 Version: 1.5.2.1

----------------------------------------
PRoConPluginEnumAssembly
    Assembly Version: 0.0.0.0
    Win32 Version: 1.5.2.1

----------------------------------------
PRoConPluginEnumAssembly
    Assembly Version: 0.0.0.0
    Win32 Version: 1.5.2.1

----------------------------------------
PRoConPluginEnumAssembly
    Assembly Version: 0.0.0.0
    Win32 Version: 1.5.2.1

----------------------------------------
Accessibility
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.9031 (WinRelRS5.050727-9000)

----------------------------------------
System.Web
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.9031 (WinRelRS5.050727-9000)

----------------------------------------
System.Design
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.9038 (WinRelRS5.050727-9000)

----------------------------------------
Ionic.Zip.Reduced
    Assembly Version: 1.9.1.5
    Win32 Version: 1.9.1.5

----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

 

I just tried this on one of my windows vms and it updated without an issue. Might have been something unique to your system setup.


The developer of the Battlefield Admin Control Panel (BFACP)

For BFACP support please post in the BFACP topic linked above.

Do not contact me via PM on the forums for help with procon. Please make a topic for it. Only PM's I will accept will revolve around any website issues.

Air VPN - The air to breathe the real Internet

Share this post


Link to post

seen it calling for this file: "C:\Users\andre\Source\Repos\AdKats\Procon-1\src\". Is this a reference to your system? That could be why it works on yours and not mine.

Share this post


Link to post

seen it calling for this file: "C:\Users\andre\Source\Repos\AdKats\Procon-1\src\". Is this a reference to your system? That could be why it works on yours and not mine.

 

Yes it is my system but I doubt it. The windows vm doesn't have a user account under that name and it was ran under the Administrator account.


The developer of the Battlefield Admin Control Panel (BFACP)

For BFACP support please post in the BFACP topic linked above.

Do not contact me via PM on the forums for help with procon. Please make a topic for it. Only PM's I will accept will revolve around any website issues.

Air VPN - The air to breathe the real Internet

Share this post


Link to post

Hmm, yeah that is odd. Maybe someone else could try to see if they run into the same issue. Running the updater manually works fine, was only when I tried to inside of procon.

Share this post


Link to post

Hello guys

 i have problem with procon cant update https://prnt.sc/q18z5y

 

Run the updater file located in the procon folder. That should work as stated above by stove3top. If not just download the one from the download section and overwrite everything in your current install folder.


The developer of the Battlefield Admin Control Panel (BFACP)

For BFACP support please post in the BFACP topic linked above.

Do not contact me via PM on the forums for help with procon. Please make a topic for it. Only PM's I will accept will revolve around any website issues.

Air VPN - The air to breathe the real Internet

Share this post


Link to post

is there any problem with this update ? i update all my insane-limits setting give error

one of m setting 

unknown.png?width=890&height=262

 

The update checker in insane limits is checking the domain "forum.myrcon.com" which no longer exists. Anything "*.myrcon.com" will not resolve.


The developer of the Battlefield Admin Control Panel (BFACP)

For BFACP support please post in the BFACP topic linked above.

Do not contact me via PM on the forums for help with procon. Please make a topic for it. Only PM's I will accept will revolve around any website issues.

Air VPN - The air to breathe the real Internet

Share this post


Link to post

is there any problem with this update ? i update all my insane-limits setting give error

one of m setting 

unknown.png?width=890&height=262

well how i solve this problem ? sorry for bad english

Share this post


Link to post

well how i solve this problem ? sorry for bad english

You would have to update the source code. It doesn't look like an issue because it's catching the exception. You can just ignore it really.

 

Sent from my ONEPLUS A5010 using Tapatalk


The developer of the Battlefield Admin Control Panel (BFACP)

For BFACP support please post in the BFACP topic linked above.

Do not contact me via PM on the forums for help with procon. Please make a topic for it. Only PM's I will accept will revolve around any website issues.

Air VPN - The air to breathe the real Internet

Share this post


Link to post

If you want the older version, download that one and transfer all your config files back to that one. Just don't click to update that one.

Share this post


Link to post

new update have so many bug . i try run old update but it auto update ! any idea how i stop the update 

 

Disable the auto-updater in the settings, close procon, then copy the old version in. Also what bugs are you talking about? If you don't tell us what they are then they can't be fixed. These bugs are related to procon client only without plugins. So far, I've seen it as stable in the regard.


The developer of the Battlefield Admin Control Panel (BFACP)

For BFACP support please post in the BFACP topic linked above.

Do not contact me via PM on the forums for help with procon. Please make a topic for it. Only PM's I will accept will revolve around any website issues.

Air VPN - The air to breathe the real Internet

Share this post


Link to post

Today and yesterday updated few Layers (6-7) working good, i will check how they will behave, then, if ok i will update the rest layers.

This link still goes to old forum https://prnt.sc/q2n7kv

 

Yeah, forgot to update that :/ Whoops

 

Please let me know if any issues happen. So far I haven't seen any on my testing servers.


The developer of the Battlefield Admin Control Panel (BFACP)

For BFACP support please post in the BFACP topic linked above.

Do not contact me via PM on the forums for help with procon. Please make a topic for it. Only PM's I will accept will revolve around any website issues.

Air VPN - The air to breathe the real Internet

Share this post


Link to post
Guest
This topic is now closed to further replies.


  • Our picks

    • Added ability to disable the new API check for player country info


      Updated GeoIP database file


      Removed usage sending stats


      Added EZRCON ad banner



      If you are upgrading then you may need to add these two lines to your existing installation in the file procon.cfg. To enable these options just change False to True.

      procon.private.options.UseGeoIpFileOnly False
      procon.private.options.BlockRssFeedNews False



       
      • 1 reply
    • I wanted I let you know that I am starting to build out the foundation for the hosting services that I talked about here. The pricing model I was originally going for wasn't going to be suitable for how I want to build it. So instead I decided to offer each service as it's own product instead of a package deal. In the future, hopefully, I will be able to do this and offer discounts to those that choose it.

      Here is how the pricing is laid out for each service as well as information about each. This is as of 7/12/2020.

      Single MySQL database (up to 30 GB) is $10 USD per month.



      If you go over the 30 GB usage for the database then each additional gigabyte is charged at $0.10 USD each billing cycle. If you're under 30GB you don't need to worry about this.


      Databases are replicated across 3 zones (regions) for redundancy. One (1) on the east coast of the USA, One (1) in Frankfurt, and One (1) in Singapore. Depending on the demand, this would grow to more regions.


      Databases will also be backed up daily and retained for 7 days.




      Procon Layer will be $2 USD per month.


      Each layer will only allow one (1) game server connection. The reason behind this is for performance.


      Each layer will also come with all available plugins installed by default. This is to help facilitate faster deployments and get you up and running quickly.


      Each layer will automatically restart if Procon crashes. 


      Each layer will also automatically restart daily at midnight to make sure it stays in tip-top shape.


      Custom plugins can be installed by submitting a support ticket.




      Battlefield Admin Control Panel (BFACP) will be $5 USD per month


      As I am still working on building version 3 of the software, I will be installing the last version I did. Once I complete version 3 it will automatically be upgraded for you.





      All these services will be managed by me so you don't have to worry about the technical side of things to get up and going.

      If you would like to see how much it would cost for the services, I made a calculator that you can use. It can be found here https://ezrcon.com/calculator.html

       
      • 10 replies
    • I have pushed out a new minor release which updates the geodata pull (flags in the playerlisting). This should be way more accurate now. As always, please let me know if any problems show up.

       
      • 9 replies
×
×
  • Create New...

Important Information

Please review our Terms of Use and Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.