Topic: Reolink WU FTP settings

[jwiegand]

For any Reolink camera users that are successfully uploading images to WU...what exact settings are you using?  I have the Reolink RLC-522 POE camera, have everything setup correctly from what I can tell and get the FTP "test succeeded" after but no images are being displayed on WU. 

My settings are:

Server address: webcam.wunderground.com
Server Port: 21
username: my webcam name given by WU
Password: my password given by WU for the camera
Upload directory: left blank
Maximum file Length: 10
File type: Picture
Interval: 5Min
Transfer Mode: PASV

I do not have any other settings that I can modify. I have the camera at the lowest possible quality settings.

Any help is appreciated!

[worachj]

I got a Reolink rcl-511w camera for Christmas but I havn't set it up yet. Found this how to setup link on their website for FTP'ing to weatherunderground.

https://support.reolink.com/hc/en-us/articles/360011989373-How-to-Set-up-FTP-for-Weather-Underground-on-Reolink-Client

Side Note: I had problems getting Email notifications until I updated the camera firmware. Make sure you have the latest and greatest firmware installed.

[jwiegand]

Thank you!  Yes I have updated the fw and followed that guide but still no luck. 

I am hoping that someone here has had there reolink cam up and running and maybe I just missed something. One thing that I noticed is that there is no place the add the file name for the images as the WU FTP configuration page shows.

[worachj]

Hope you get it working so you can give me the steps to set mine up. 

[jwiegand]

me too!

[galfert]

Have you tried FTPing this image to your own local computer or ftp server? I recommend doing this and taking a look at how large the image is?
My suspicion is that the file is too big. If you reduce the resolution of the camera then the still shot image will be smaller and then it may be sufficient to pass as an acceptable image size for WU FTP uploading.

But the best solution is to use something else to capture the image via the camera's URL still shot caputure feature (no FTP)...then you upload the image using an FTP script or program. These other solutions will be able to manipulate the image and reduce the size. This allows you to still enjoy the local direct access to the camera in full resolution.

[jwiegand]

That is my next step. I’m suspecting this may be the issue as well. 

[worachj]

Getting the same result as you above, no image uploaded yet.

Got success linking my RLC-511w camera to my WU weather station and successfully complete an FTP test within the Reolink windows program, but no image shows up on WU yet. Going to wait a day and see if it shows up.

The FTP test within the widow’s program was only successful with the ‘Transfer Mode’ setting set to PORT, couldn’t get the other transfer mode settings to work. Otherwise, all the other settings were the same as yours above.

[jwiegand]

Bummer.  Hopefully WU will show images soon or hopefully someone that has a similar working setup will chime in.

[worachj]

Slowly getting up to speed with the rest of you!

Used the below link to capture a live image from my camera and found out the image size is always around 350KB. So, if WU has a 150KB limit then the image is too big.

https://support.reolink.com/hc/en-us/articles/360007011233-How-to-Capture-Live-JPEG-Image-of-Reolink-Cameras-via-Web-Browsers

Not sure what I'm going to do next. Sending a image to WU is not that important to me, just wanted to see if it could be done with my camera.

[SoMDWx]

I have several Reolink cameras and use IPTimeLapse to upload to WU... works very well...

[worachj]

 My camera is still showing as off line on WU under My Devices. I wouldn’t think sending too large of an image would affect the online/offline status. Something isn’t right with WU and the camera … guessing there’s still a WU problem with cameras.

Added Edit:Thinking there's a problem with WU webcam server. Servers not listening ... getting timeout.

Code: [Select]

C:\>tracert webcam.wunderground.com
Tracing route to webcam.wunderground.com [52.37.52.183]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Merlin [192.168.1.1]
  2     8 ms     9 ms     8 ms  96.120.116.201
  3     8 ms     8 ms     9 ms  po-301-1209-rur01.eagan.mn.minn.comcast.net [68.87.179.161]
  4     7 ms     8 ms     7 ms  po-2-rur02.eagan.mn.minn.comcast.net [68.86.233.58]
  5     9 ms    10 ms    10 ms  be-16-ar01.roseville.mn.minn.comcast.net [68.86.233.93]
  6    19 ms    21 ms    20 ms  be-13367-cr02.350ecermak.il.ibone.comcast.net [68.86.94.81]
  7    19 ms    19 ms    19 ms  be-1102-cs01.350ecermak.il.ibone.comcast.net [96.110.36.97]
  8    20 ms    20 ms    20 ms  be-1111-cr11.350ecermak.il.ibone.comcast.net [96.110.35.2]
  9    33 ms    34 ms    34 ms  be-302-cr11.1601milehigh.co.ibone.comcast.net [96.110.37.150]
 10    34 ms    34 ms    34 ms  be-1311-cs03.1601milehigh.co.ibone.comcast.net [96.110.39.73]
 11    34 ms    33 ms    35 ms  be-3302-pe02.910fifteenth.co.ibone.comcast.net [96.110.38.122]
 12    33 ms    32 ms    34 ms  23.30.206.238
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.

[jwiegand]

Yea looks like.

I’m m getting “FTP success” with the current upload settings but my camera shows as offline and no images are being displayed on WU.  When I save an image and check the size, it’s well under 150Kb. Have no idea how to proceed from here. 

[galfert]

Another suggested tip is that the upload image file should be called image.jpg and perhaps some cameras use a different name and worse yet many probably do not have the mechanism to allow the file name to be chosen.

[jwiegand]

Another suggested tip is that the upload image file should be called image.jpg and perhaps some cameras use a different name and worse yet many probably do not have the mechanism to allow the file name to be chosen.

Yes in the FTP settings of my Reolink Cam, there is do image file name setting. Could be part if it. Strange since Reolink has a WU webcam tutorial.

[davidmc36]

Not a Reolink but these settings are working right now.

 [ You are not allowed to view attachments ]  [ You are not allowed to view attachments ]

[worachj]

When I do a TRACERT of 'webcam.wunderground.com' it times out at the Amazon server banks in Chicago. Guessing working webcams are going thru a different server bank.

Can someone with a working webcam to WU post their 'Tracert webcam.wunderground.com' results here for me.

THANKS!

[davidmc36]

This is what I got:

Code: [Select]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Carolyn Colpitts>tracert webcam.wunderground.com

Tracing route to webcam.wunderground.com [52.36.136.128]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  mynetwork [192.168.2.1]
  2     6 ms     6 ms     6 ms  10.11.33.41
  3     *        *        *     Request timed out.
  4    12 ms     7 ms    15 ms  tcore4x-ottawa23_bundle-ether14.net.bell.ca [64.
230.53.96]
  5     7 ms    25 ms     7 ms  dis32-ottawa23_ae1.net.bell.ca [64.230.51.71]
  6    71 ms    71 ms    71 ms  tcore3x-ottawa23_bundle-ether7.net.bell.ca [64.2
30.51.68]
  7    68 ms    74 ms    70 ms  tcore4-ottawatc_hundredgige0-1-0-0.net.bell.ca [
64.230.50.164]
  8    66 ms    66 ms    67 ms  tcore4-toronto63_hundredgige1-5-0-0.net.bell.ca
[64.230.50.93]
  9    80 ms    71 ms    71 ms  tcore4-toronto63_pos0-0-0-0_core.net.bell.ca [64
.230.160.186]
 10    64 ms    67 ms    65 ms  tcore4-vancouver_hundredgige0-1-0-0.net.bell.ca
[64.230.79.67]
 11    67 ms    65 ms    65 ms  bx2-vancouver_et7-1-0.net.bell.ca [64.230.123.35
]
 12    70 ms    72 ms    70 ms  99.82.181.90
 13    72 ms    75 ms    84 ms  52.93.75.88
 14    70 ms    74 ms    69 ms  52.93.75.97
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

C:\Users\Carolyn Colpitts>

[davidmc36]

Trying out the IP route:

https://www.wxforum.net/index.php?topic=33651.msg375454#msg375454

I didn't wait for this to finish. Im guessing will result in the same.

Code: [Select]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Carolyn Colpitts>tracert 52.36.136.128

Tracing route to ec2-52-36-136-128.us-west-2.compute.amazonaws.com [52.36.136.128]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  mynetwork [192.168.2.1]
  2    12 ms     6 ms     7 ms  10.11.33.41
  3     *        *        *     Request timed out.
  4    14 ms    15 ms    15 ms  tcore4x-ottawa23_bundle-ether14.net.bell.ca [64.230.53.96]
  5     8 ms     8 ms     7 ms  dis32-ottawa23_ae1.net.bell.ca [64.230.51.71]
  6    71 ms    71 ms    71 ms  tcore3x-ottawa23_bundle-ether7.net.bell.ca [64.230.51.68]
  7    63 ms    62 ms    64 ms  tcore4-ottawatc_hundredgige0-1-0-0.net.bell.ca [64.230.50.164]
  8    65 ms    67 ms    67 ms  tcore4-toronto63_hundredgige1-5-0-0.net.bell.ca [64.230.50.93]
  9    77 ms    73 ms    77 ms  tcore4-toronto63_pos0-0-0-0_core.net.bell.ca [64.230.160.186]
 10    70 ms    67 ms    68 ms  tcore4-vancouver_hundredgige0-1-0-0.net.bell.ca [64.230.79.67]
 11    65 ms    68 ms    66 ms  bx2-vancouver_et7-1-0.net.bell.ca [64.230.123.35]
 12    70 ms    69 ms    70 ms  99.82.181.90
 13    71 ms    70 ms    73 ms  52.93.75.88
 14    70 ms    71 ms    71 ms  52.93.75.97
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17  ^C
C:\Users\Carolyn Colpitts>
Just times out with the other IP's also.

Code: [Select]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Carolyn Colpitts>tracert 52.36.136.128

Tracing route to ec2-52-36-136-128.us-west-2.compute.amazonaws.com [52.36.136.128]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  mynetwork [192.168.2.1]
  2    12 ms     6 ms     7 ms  10.11.33.41
  3     *        *        *     Request timed out.
  4    14 ms    15 ms    15 ms  tcore4x-ottawa23_bundle-ether14.net.bell.ca [64.230.53.96]
  5     8 ms     8 ms     7 ms  dis32-ottawa23_ae1.net.bell.ca [64.230.51.71]
  6    71 ms    71 ms    71 ms  tcore3x-ottawa23_bundle-ether7.net.bell.ca [64.230.51.68]
  7    63 ms    62 ms    64 ms  tcore4-ottawatc_hundredgige0-1-0-0.net.bell.ca [64.230.50.164]
  8    65 ms    67 ms    67 ms  tcore4-toronto63_hundredgige1-5-0-0.net.bell.ca [64.230.50.93]
  9    77 ms    73 ms    77 ms  tcore4-toronto63_pos0-0-0-0_core.net.bell.ca [64.230.160.186]
 10    70 ms    67 ms    68 ms  tcore4-vancouver_hundredgige0-1-0-0.net.bell.ca [64.230.79.67]
 11    65 ms    68 ms    66 ms  bx2-vancouver_et7-1-0.net.bell.ca [64.230.123.35]
 12    70 ms    69 ms    70 ms  99.82.181.90
 13    71 ms    70 ms    73 ms  52.93.75.88
 14    70 ms    71 ms    71 ms  52.93.75.97
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17  ^C
C:\Users\Carolyn Colpitts>tracert 54.148.11.142

Tracing route to ec2-54-148-11-142.us-west-2.compute.amazonaws.com [54.148.11.142]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  mynetwork [192.168.2.1]
  2     6 ms     6 ms     7 ms  10.11.33.41
  3     *        *        *     Request timed out.
  4    11 ms    15 ms     7 ms  tcore3x-ottawa23_bundle-ether14.net.bell.ca [64.230.53.98]
  5     7 ms     7 ms     7 ms  dis33-ottawa23_ae0.net.bell.ca [64.230.51.73]
  6    73 ms    71 ms    80 ms  tcore3x-ottawa23_bundle-ether8.net.bell.ca [64.230.51.72]
  7    67 ms    64 ms    64 ms  tcore4-ottawatc_hundredgige0-1-0-0.net.bell.ca [64.230.50.164]
  8    62 ms    71 ms    79 ms  tcore4-toronto21_hundredgige2-4-0-2.net.bell.ca [64.230.74.9]
  9    68 ms    67 ms    68 ms  tcore4-toronto47_be10.net.bell.ca [64.230.53.91]
 10    62 ms    60 ms    60 ms  tcore2-vancouver_et0-0-0.net.bell.ca [64.230.52.233]
 11    60 ms    61 ms    60 ms  bx2-vancouver_et7-1-0.net.bell.ca [64.230.123.35]
 12    68 ms    66 ms    65 ms  99.82.181.90
 13    66 ms    74 ms    64 ms  52.93.75.120
 14    65 ms    66 ms    67 ms  52.93.75.129
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

C:\Users\Carolyn Colpitts>tracert 52.37.52.183

Tracing route to ec2-52-37-52-183.us-west-2.compute.amazonaws.com [52.37.52.183]
over a maximum of 30 hops:

  1     5 ms     2 ms     1 ms  mynetwork [192.168.2.1]
  2    13 ms    19 ms     6 ms  10.11.33.41
  3     *        *        *     Request timed out.
  4    11 ms    20 ms    15 ms  tcore4x-ottawa23_bundle-ether14.net.bell.ca [64.230.53.96]
  5    11 ms     7 ms     7 ms  dis32-ottawa23_ae1.net.bell.ca [64.230.51.71]
  6    75 ms    71 ms    71 ms  tcore3x-ottawa23_bundle-ether7.net.bell.ca [64.230.51.68]
  7    70 ms    71 ms    70 ms  tcore4-montreal01_0-14-0-0.net.bell.ca [64.230.79.125]
  8    69 ms    72 ms    70 ms  tcore4-toronto12_bundle-ether33.net.bell.ca [64.230.78.190]
  9    68 ms    65 ms    64 ms  tcore4-vancouver_hundredgige0-1-0-0.net.bell.ca [64.230.79.67]
 10    65 ms    65 ms    65 ms  bx2-vancouver_et7-1-0.net.bell.ca [64.230.123.35]
 11   674 ms    70 ms    70 ms  99.82.181.90
 12    75 ms    66 ms    67 ms  52.93.75.56
 13    71 ms    70 ms    70 ms  52.93.75.67
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

C:\Users\Carolyn Colpitts>

[worachj]

Trying out the IP route:

Thanks for you reply's!

[worachj]

Thought I read somewhere that WU servers are part of the Amazon server banks.  Not sure what I'm doing.

The working camera's TRACERT webcam.wunderground.com makes it to the Amazon servers in Montreal before timing out.

My non-working camera's TRACERT webcam.wunderground.com makes it to the Comcast servers in Los Angles before timing out. Never makes it to the Amazon servers.

Since my camera shows as offline in WU My Devices ... I'm thinking my camera's FTP's requests are just being ignored by WU until it gets online.

Need to figure out why my camera is showing as offline, why does WU thinks the camera is offline!


https://www.whatismyip.com/ip-address-lookup/

[galfert]

If you open a command prompt in Windows (run cmd), you can test DNS resolution of web addresses. You do his with the nslookup command.

nslookup webcam.wunderground.com

That will return all the possible IP addresses using your default DNS server settings on your network. You can change what DNS your network uses in your router. I prefer to not use the automatic default ISP given DNS servers and I manually enter Google's DNS servers into my router. But you don't have to change your router settings to test the results of a different DNS server. If you want to test Google's DNS servers you can specify them in the nslookup command as follows.

nslookup webcam.wunderground.com 8.8.8.8

Google's DNS servers are 8.8.8.8 and 8.8.4.4. But you can also use Cloudflare 1.1.1.1 and 1.0.0.1. There are others yet but those are the most popular.

When you see the DNS results for the domain if you repeat the command you'll notice that the resulting IP addresses changes order. This is a randomization so that multiple servers share the load of the services being offered. Often though as has been notorious with WU is that some of these IP addresses are not working servers, which means that some uploads will fail depending on which server address you happen to of gotten for that instant. There was a old thread that was maintained by a forum member some time ago to keep track of which of these WU IP addresses were working and which weren't. This way people could set their WU webcam upload to the working server address instead of using the URL name, because the URL name was going to randomly give you an address from the set.

[worachj]

I'm using Comcast's DNS Servers:
DNS1: 75.75.75.75
DNS2: 75.75.75.76

My nslookup of webcam.wunderground.com gets resolved to the Amazon servers. I may try using other DNS servers.
Thanks!

Code: [Select]

Microsoft Windows [Version 10.0.19042.685](c) 2020 Microsoft Corporation. All rights reserved.

C:\>nslookup webcam.wunderground.com
Server:  UnKnown
Address:  2601:441:8700:1bbc:cad7:19ff:fe4b:145d

Non-authoritative answer:
Name:    webcam.wunderground.com
Addresses:  54.148.11.142
          52.36.136.128
          52.37.52.183



[worachj]

Changed to Googles DNS server 8.8.8.8 and got same results. I'll start testing again.

Code: [Select]

Microsoft Windows [Version 10.0.19042.685]
(c) 2020 Microsoft Corporation. All rights reserved.

C:\>nslookup webcam.wunderground.com
Server:  Merlin.hsd1.mn.comcast.net
Address:  192.168.1.1

Non-authoritative answer:
Name:    webcam.wunderground.com
Addresses:  54.148.11.142
          52.36.136.128
          52.37.52.183




[galfert]

I wasn't suggesting that changing to Google's DNS was a solution for the WU webcam uploads. People change to Google's DNS servers for faster Internet due to faster name resolution, and also more reliable than the ISP DNS servers. I only offered the DNS nslookup command as a way to demonstrate what is happening on your computer behind the scenes. This would enable you to find out what the webcam upload IP addresses are and to use those instead of the named URL. Do keep in mind that if you hard code an IP address for the upload that the working server for WU may change and it might be something that you have to continually monitor and react to with manual changes to the upload settings.