Reset Search
 

 

Article

EGuest - Adopting controller throwing the following error: ERROR: unable to communicate to Eguest server [x.x.x.x:443] - 'utf8' codec can't decode byte 0xb3 in position 4: invalid start byte

« Go Back

Information

 
TitleEGuest - Adopting controller throwing the following error: ERROR: unable to communicate to Eguest server [x.x.x.x:443] - 'utf8' codec can't decode byte 0xb3 in position 4: invalid start byte
Symptoms
When configuring the adopting controller to communicate with EGuest appliance, the following error appears on the adopting controller logs.
Aug 13 10:01:35 2019: %USER-3-ERR: main.pyo: * * ERROR: unable to communicate to Eguest server [x.x.x.x:443] - 'utf8' codec can't decode byte 0xb3 in position 4: invalid start byte
Aug 13 10:03:15 2019: %USER-3-ERR: main.pyo: * * ERROR: unable to communicate to Eguest server [x.x.x.x:443] - 'utf8' codec can't decode byte 0xb3 in position 4: invalid start byte
Aug 13 10:04:55 2019: %USER-3-ERR: main.pyo: * * ERROR: unable to communicate to Eguest server [x.x.x.x:443] - 'utf8' codec can't decode byte 0xb3 in position 4: invalid start byte
Aug 13 10:06:35 2019: %USER-3-ERR: main.pyo: * * ERROR: unable to communicate to Eguest server [x.x.x.x:443] - 'utf8' codec can't decode byte 0xb3 in position 4: invalid start byte
Aug 13 10:08:15 2019: %USER-3-ERR: main.pyo: * * ERROR: unable to communicate to Eguest server [x.x.x.x:443] - 'utf8' codec can't decode byte 0xb3 in position 4: invalid start byte
Aug 13 10:09:55 2019: %USER-3-ERR: main.pyo: * * ERROR: unable to communicate to Eguest server [x.x.x.x:443] - 'utf8' codec can't decode byte 0xb3 in position 4: invalid start byte

 
Environment
  • All Summit WM3000 Series Controllers
  • ExtremeWiNG Controllers
  • WirelessWiNG Controllers
  • ExtremeWiNG Access Points
  • WirelessWiNG Acess Points
  • WiNG v5.9.5 Software
  • ExtremeGuest
  • EGuest
  • ExtremeGuest v5.9.3.1 Software
Cause
The switch hostname where some of the APs are connected has unrecognizable characters leading to an information parsing problem when the controller is trying to reach the EGuest appliance.
Resolution
Disabling LLDP/CDP on AP profile allowed the string to get correctly parsed and the connection between the controller and the EGuest appliance was restored.
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255