Posts made by nodders

Just to close this out, got in touch with support with some screenies who identified that my http/https ports were closed. Current version of the Windows App does not have this feature to enable them, but the next version will do. They sent me the beta version and all is good now. Also fixed the Surveillance Station issue, so those with problems getting Synology SS to find/identify their camera (I think it looks on port 80/443) likely this is the fix too. So for those with a similar issue, suggest either wait until next version of Windows App to see if that fixes it, or get in touch with support. Thank you to @reolink-fiona for taking the time to consider - looks like your original query was right, just a software functionality issue.

@reolink-fiona Thanks for getting back to me and the suggestion. I've now raised a support ticket. If I get a solution, I'll put it back in here in case anyone else is having/will have this issue

@reolink-fiona Thanks for the tip. Unfortunately I found those settings before and have tried turned all ports/protocols on but that did not work either.

I knew there was something I was was forgettng to add to that list in my original post.

If you scroll to the right of this comparison screen you should get some indicators (scroll bar at the bottom, not that obvious to find).#
https://reolink.com/comparison/#wifi

You can dig into further details in the individual spec pages:

• 511: https://reolink.com/product/rlc-511wa/?attribute_pa_version=1-pack#specifications
• 510:https://reolink.com/product/rlc-510wa/?attribute_pa_version=1-pack#specifications

From what I can see, the RLC-511A is more expensive but comes with more features, namely a spotlight, colour night vision, a 5x optical zoom, with it a variable viewing angle, and 2-way audio. It is also larger and heavier (80x72x238mm and 838g for the 511 v 67x186mm and 415g for the 510). I haven't dig into it (the above should say) but the 410W lacking the A postfix probably lacks some of the autotracking features of the other two.

Hope that helps

Hi,

I'm unable to access the web interface of my RLC-510WA. Every time I do I get a mostly blank webpage with the message "500 Internal Server Error" and "nginx". I am however able to access the camera via the PC application and the Android smartphone app so the camera is on and functioning, it is just this mode of connection that seems to be awry.

I've followed the guidance on the Reolink site namely:

• this: https://support.reolink.com/hc/en-us/articles/360003452893-How-to-Access-Reolink-Cameras-Locally-via-a-Web-Browser
• and this: https://support.reolink.com/hc/en-us/articles/900002172886-Failed-to-Access-Cameras-NVRs-via-Web-Browser-in-LAN

but none of the issues have helped

Some other points:

1. The camera is up-to-date re firmware available on the download section for this camera - v3.1.0.764_21121712 on the PC app info screen
2. I am trying this on the same WiFi LAN re PCs. All other devices that should be contactable are. I have not set up any VLANs or similar.
3. I do run Pihole and I've turned that all off and reset the DNS settings to default to see if there is a difference, but no joy
4. I've tried via different PCs, some running Windows, some running Linux; and on devices (tablets and phones) - all with the same outcome
5. I've tried different browsers - Chrome, Firefox and Edge. Again all the same outcome.
6. I've tried both HTTP and HTTPS interfaces as per the guidance as above, same outcome
7. I also have issues getting my Synology NAS Surveillance Station to recognise the device on a Search - I can however manually add it but only as a ONVIF device
8. On which note, when I tried and access the camera via a browser on its ONVIF port, I do get a page full of markup, so ONVIF seems to work, it is just HTTP and HTTPS that is the issue
9. I've tried rebooting the camera, resetting config etc
10. I have not done a full factory reset - I can't bring myself to unscrew the camera to plug it in to ethernet re setting up initial wifi)
11. As noted above, the PC application and Android app can access the camera with full functionality.

Given the apps work, why do I see this as an issue? Given one of thestandard ways of interfacing with the camera is not working, then obviously something is amiss and I would rather know what it was than ignore it. I also think it might be something related to point 4 above re Surveillance Station, but that is a side issue.

Anyone any advice or ideas?