200H: Device Registration Status: Not Registered
bbp
Posts: 65 Ally Member
Last few days this happens a lot.
0
All Replies
-
You need to improve on that. People rely on security services.
0 -
run
tracetcp he.myzyxel.com:443
tracetcp auth-mtls.api.cloud.zyxel.com:443
also ping checks look to be done by TCP 4335
0 -
Hi Peter, I have no problem reaching he.myzyxel.com. (traceroute -n -p 443 -T he.myzyxel.com)
Problem is target responds with 'status code 500' when 200H is querying it via API. That's internal server error (codes 5xx) on target side.
0 -
Hi @bbp,
May I know if this issue occurred on the device that has been registered? If not, could you send the MAC address and Serial number of that device to check?
0 -
Yes, device was previously registered. Sent you serial and MAC in private message.
0
Categories
- All Categories
- 415 Beta Program
- 2.4K Nebula
- 144 Nebula Ideas
- 94 Nebula Status and Incidents
- 5.6K Security
- 237 USG FLEX H Series
- 267 Security Ideas
- 1.4K Switch
- 71 Switch Ideas
- 1.1K Wireless
- 40 Wireless Ideas
- 6.3K Consumer Product
- 247 Service & License
- 384 News and Release
- 83 Security Advisories
- 29 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.2K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 83 About Community
- 71 Security Highlight