200H: Device Registration Status: Not Registered

bbp
bbp Posts: 68  Ally Member
First Answer First Comment Friend Collector Sixth Anniversary

Last few days this happens a lot.

Nebila status 500.jpg

All Replies

  • bbp
    bbp Posts: 68  Ally Member
    First Answer First Comment Friend Collector Sixth Anniversary

    You need to improve on that. People rely on security services.

    No security services.jpg
  • PeterUK
    PeterUK Posts: 3,775  Guru Member
    100 Answers 2500 Comments Friend Collector Seventh Anniversary
    edited October 2024

    run

    tracetcp he.myzyxel.com:443

    tracetcp auth-mtls.api.cloud.zyxel.com:443

    also ping checks look to be done by TCP 4335

  • bbp
    bbp Posts: 68  Ally Member
    First Answer First Comment Friend Collector Sixth Anniversary

    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.

  • Zyxel_Melen
    Zyxel_Melen Posts: 3,229  Zyxel Employee
    Zyxel Certified Network Engineer Level 1 - Switch Zyxel Certified Network Administrator - Switch Zyxel Certified Network Administrator - Nebula Zyxel Certified Sales Associate

    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?

    Zyxel Melen


  • bbp
    bbp Posts: 68  Ally Member
    First Answer First Comment Friend Collector Sixth Anniversary

    Yes, device was previously registered. Sent you serial and MAC in private message.