1. Community
  2. Plugin Support
  3. Discord Messages
JsonReaderException: Unexpected character encountered while parsing valueError
Plugin Page
Posted 6 years ago
Last updated 6 years ago
#1
Did not change anything in the server and today it seems like that all http requests fail, they work fine in a browser but not in server, here is an example error I am getting:

20:46 [Error] Web request callback raised an exception in 'DiscordMessages' plugin (JsonReaderException: Unexpected character encountered while parsing value: E. Path '', line 0, position 0.)
at Newtonsoft.Json.JsonTextReader.ParseValue () [0x002b3] in <8fe7f8665ff548909c2f26d557e5093a>:0
at Newtonsoft.Json.JsonTextReader.Read () [0x0004c] in <8fe7f8665ff548909c2f26d557e5093a>:0
at Newtonsoft.Json.Linq.JObject.Load (Newtonsoft.Json.JsonReader reader, Newtonsoft.Json.Linq.JsonLoadSettings settings) [0x00013] in <8fe7f8665ff548909c2f26d557e5093a>:0
at Newtonsoft.Json.Linq.JObject.Parse (System.String json, Newtonsoft.Json.Linq.JsonLoadSettings settings) [0x0000c] in <8fe7f8665ff548909c2f26d557e5093a>:0
at Newtonsoft.Json.Linq.JObject.Parse (System.String json) [0x00000] in <8fe7f8665ff548909c2f26d557e5093a>:0
at Oxide.Plugins.DiscordMessages+<Request>c__AnonStorey0.<>m__1 (System.Int32 code, System.String response) [0x0001c] in <0e72078987ed4224a077e7d1105a8fc2>:0
at Oxide.Core.Libraries.WebRequests+WebRequest.<OnComplete>b__42_0 () [0x00034] in <b0a93b504f034a0db8b1c3d2503c0987>:0
Any ideas?
Posted 6 years ago
Last updated 6 years ago
#2
This error is not particular to this plugin, a standard web request fails as well but it works in web browser!
Posted 6 years ago
Last updated 6 years ago
#3
Sounds like something is blocking those connections on the machine then, there's no other reason really.
Posted 6 years ago
Last updated 6 years ago
#4
But they work fine in the browser when I test ..
Firewalls are disabled in services
Posted 6 years ago
Last updated 6 years ago
#5
Right, but the browser is a separate application than the server.
Posted 6 years ago
Last updated 6 years ago
#6
Ok, so if browser works, cmd line curl command works but not umod client, who to blame?
Posted 6 years ago
Last updated 6 years ago
#7
Herro
Ok, so if browser works, cmd line curl command works but not umod client, who to blame?
There is no "umod client", it is part of the server provided by Rust; Oxide plugins just utilize it. Since this seems to be an isolated issue to 1 server, you, it's safe to say that there's something blocking those connections if they are all failing. This particular example in your first post does not look like a blocked connection though, rather an unhandled response.
Posted 6 years ago
Last updated 6 years ago
#8
I have a feeling you're right about that, I am checking with host, is it possible that its blocking empty http agent requests from the client? and if so is there a way to get around that by sending a fake agent?
Posted 6 years ago
Last updated 6 years ago
#9
Herro
I have a feeling you're right about that, I am checking with host, is it possible that its blocking empty http agent requests from the client? and if so is there a way to get around that by sending a fake agent?

I doubt they would be blocking the connection for that, you'd see a very difference response generally too.