I getting from many plugin's following error:

Error: ConnectFailure (TLS Support not available.)

Plugins who outputting this error: Discord Extension or the core of uMod/OXIDE if the compiler not avaible

ex. after a fresh installation i get this error:

Error: ConnectFailure (TLS Support not available.)
Exception while starting compiler version Unknown: (Win32Exception: ApplicationName='/home/AMP/.ampdata/instances/rust/rust/258550/Compiler.x86_x64', CommandLine='/service /logPath:/home/AMP/.ampdata/instances/rust/rust/258550/oxide/logs', CurrentDirectory='', Native error= Cannot find the specified file) at System.Diagnostics.Process.StartWithCreateProcess (System.Diagnostics.ProcessStartInfo startInfo) [0x002dc] in <3845a180c26b4889bc2d47593a665814>:0 at System.Diagnostics.Process.Start () [0x0003a] in <3845a180c26b4889bc2d47593a665814>:0 at (wrapper remoting-invoke-with-check) System.Diagnostics.Process.Start() at Oxide.Plugins.PluginCompiler.CheckCompiler () [0x001f3] in <9affce1cd15c4ec183941adef8db1722>:0 ​

My hoster say's its the Controll Panel AMP (cubecoders) the support of amp say's its an bug of uMod/OXIDE.

uMod/Oxide does not provide the actual web handling, that is provided by the game you are trying to utilize it with and the server itself. Many games use an older Mono version, which often do not support modern web technology. In your case, the Compiler is attempted to be download through what the game provides but is unable to be due to TLS not being supported on your server/setup for some reason.

@Wulf

1. NICE profile pic! :D

2. I try to run an rust instance (oxide/umod)

I'd suggest checking on your server for the MONO_TLS_PROVIDER environment variable to see if/what it is set to. The issue you are having is not really related to Oxide itself, just that something is set on your server that is preventing the Mono version that comes with the game from connecting to any site using TLS for their HTTPS connection.

The URL we use with downloading our plugin compiler (Compiler.exe, Compiler.x86, and Compiler.x86_x64) is https://nyc3.digitaloceanspaces.com/umod-01/ which supports TLS 1.0, 1.1, and 1.2. We've been using this URL for at least half a year at this point, so we know that it isn't an issue with the URL as it is actively used daily during installs and update checks to the compiler.

@Wulf

How did i get this 'MONO_TLS_PROVIDER'

i try'd echo $MONO_TLS_PROVIDER but the output was nothing

and to make the server running i used the file from https://github.com/theumod/Compiler this site and pastet in the oxide folder now it works but i getting farther the error with tls... (sry 4 my bad english im from germany)

Installing the compiler manually only fixes it being missing, it won’t fix your server being unable to connect to HTTPS sites, such as the one they we use for checking for updates for the compiler.

@Wulf
And what is with

How did i get this 'MONO_TLS_PROVIDER'

i try'd echo $MONO_TLS_PROVIDER but the output was nothing

@SpieleArena try installing glib-networking
Here is a valid value of the environment variable to try as well

MONO_TLS_PROVIDER=legacy

You can set it by typing..
export MONO_TLS_PROVIDER=legacy

There may be some others..

Also you can try importing certificates

mozroots --import --sync --url "http://hg.mozilla.org/releases/mozilla-release/raw-file/default/security/nss/lib/ckfw/builtins/certdata.txt

@Calytic

glip-networking is now installed but i have the same error. :(


i also tryd your other sulutions but same result

Merged post

Nobody can help me? :c

Those are the only solutions we have at this time. The issue isn’t really an Oxide issue, sounds like the control panel you are using is setting something as I’ve not seen that issue with any other host or setup.

The CubeCoder developer did mention that they added a possible fix/change that I mentioned above, so our may want to check with them again.