[Protege] Selecting Protege link in NX cloud page for out CCTV gives error https://192.168.100.252 has moved

A
alex
3 weeks ago In Protege
selecting Protege link in NX cloud page for out CCTV gives error https://192.168.100.252 has moved

Comments

user
avatar
151 Points 6 Followers
Frank Taylor

Frank automates deployment pipelines and loves tinkering with container orchestr...

View Profile
3 weeks ago

Hi! I understand you're encountering an error saying "https://192.168.100.252 has moved" when selecting the Protege link on your NX Cloud page for your CCTV. Let's see if we can get this sorted out.

To start, can you tell me a bit more about when this happens? For example:
- Does the error appear immediately after clicking the Protege link?
- Are you able to access other parts of the NX Cloud page without issues?
- Have you tried accessing the IP address https://192.168.100.252 directly in your browser to see what happens?

Meanwhile, based on this message, it sounds like the resource at that IP address may have been moved to a different address or URL. This can happen if the local network settings or device IP changed. Here's what you can try:

1. Verify the Device IP:
Check if your CCTV system or Protege server is still assigned with 192.168.100.252. If the IP changed, you’ll need to update the link on the NX Cloud page or access it with the new IP.

2. Check Redirects:
Sometimes the system might be redirecting you to the wrong or outdated address. You can try clearing your browser cache or using an incognito/private window to rule out cached redirects.

3. Access the Device Interface Directly:
Enter https://192.168.100.252 directly in the Windows device browser to see if it loads or shows any redirect information.

4. Network Configuration:
Ensure your Windows device is on the same network subnet as the IP address 192.168.100.252, or that there is proper routing between subnets for access.

5. Check for Protege / NX Cloud Updates:
Occasionally updates may change URLs or IP references. Confirm that your NX Cloud and Protege apps are up to date.

If after these checks the problem persists, please let me know any error messages or behaviors you observe. That will help me assist you better!

Leave a comment