NotSupportedException: The URI prefix is not recognizedNot An Issue

The host I am using is having an Url exception error that is casuing Oxide to load and Oxide.version works but the plugins do not load and .JSON are not created. They have been trying to fix it for about 4 days since the last update. Does anyone have any Idea on what could be causing this or a way to fix it? 

The Error in oxide Log.

03:26 [Error] Web request produced exception (Url: https://www.google-analytics.com/collect) (NotSupportedException: The URI prefix is not recognized.)
at System.Net.WebRequest.Create (System.Uri requestUri, System.Boolean useUriBase) [0x000ae] in <14e3453b740b4bd690e8d4e5a013a715>:0
at System.Net.WebRequest.Create (System.String requestUriString) [0x00014] in <14e3453b740b4bd690e8d4e5a013a715>:0
at Oxide.Core.Libraries.WebRequests+WebRequest.Start () [0x00014] in <ec05e0208c9149bba43236ca58fea105>:0

That error would be an indication that there's a network issue with your server, which isn't something Oxide can fix.

Is this something that a user can fix or must it be done on the Hosts level? Is there anyway I can go about fixing this myself? Firewall settings ect.? 

Have you tried restarting the server?

Yes I have. I have also reinstalled Oxide both with the updater they have and manually about 8 times and still nothing. This has been an issue since the Feb 4th update. The only thing I could really adjust on my end is firewall/allowed connections settings for manually ading Ips that can be connected.

The update wouldn't have changed anything with that functionaltiy, webrequests and anything related to the Oxide core itself hasn't been changed in years.

Yeah I will just have to wait for the server hosting company to sort it out. I am not sure what the issue is on their end but It just recently started on the 4th. For whatever reason all of their Oxide servers are now not handling webrequests and it seems like they are not sure why.

Could be something changed with their server setup that is causing it to error. Definitely nothing wrong with the URL in the error.

Locked automatically