External Website not updating.

[Monica Mulholland]

I am running Weewx on a RPi3 and have been for a number of years. It recently stopped updating the external website - see attached.

On investigation, I found that the internal website was working perfectly - see attached.

I complained to my company hosting my website and this is what they have to say - see attachment.

Has anything changed in Weewx that might have caused this.

As an aside, for the last couple of years I have been getting this message when updating my Pi.

pi@WeatherPi:~ $ sudo apt-get update && sudo apt-get upgrade
Hit:1 http://weewx.com/apt squeeze InRelease                        
Ign:2 http://raspbian.raspberrypi.org/raspbian stretch InRelease        
Hit:3 http://archive.raspberrypi.org/debian stretch InRelease            
Err:4 http://raspbian.raspberrypi.org/raspbian stretch Release                
  404  Not Found [IP: 93.93.128.193 80]
Reading package lists... Done                      
E: The repository 'http://raspbian.raspberrypi.org/raspbian stretch Release' does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
pi@WeatherPi:~ $

Does this have any bearing? It should not have because I have been getting the message for quite a while and the failure to update the site has only happened recently.

I am a bit mystified as to what is going on. Any help would be much appreciated.

[Tom Keffer]

Nothing has changed in WeeWX that would cause this. And, frankly, the message from your hosting company is completely useless.

To diagnose we would need to see the log. See the wiki article Help! Posting to weewx-user for instructions on getting a good copy of the log.

Security updates of 'stretch' were discontinued about 4 years ago. That may explain why you are getting the IP not found error. It's also possible that your /etc/sources.list file uses IP addresses, rather than domain names, and that address has been retired. In any case, that's a Debian issue, not a WeeWX issue.

-tk

--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/86231e99-aea3-4380-8d9a-c5e146aa2a75n%40googlegroups.com.

[Monica Mulholland]

Thank you for that!

Presumably I use the last one on the list (why are there two....and why are there so many?...I would have imagined that only the latest one was kept?!?!)

[Tom Keffer]

Sorry, I blew it. For the IP error, you want to take a look in /etc/apt/sources.conf.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/46336e2c-5f1a-4767-96d8-0d7da33f5780n%40googlegroups.com.

[Monica Mulholland]

Hope this helps.

[Monica Mulholland]

No worries...that is part 2 of the problem...I hope!

On Friday 5 July 2024 at 11:35:34 UTC+12 Tom Keffer wrote:

[Monica Mulholland]

This is what is in sources.list.....nothing in sources.conf

On Friday 5 July 2024 at 11:35:34 UTC+12 Tom Keffer wrote:

[Tom Keffer]

You need to let it run for at least an archive interval. Your archive interval has been set to 10 minutes, and you let it run for only 6 minutes. Patience!

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/7504487b-9849-4dfa-b8a7-2f3e747118den%40googlegroups.com.

[Monica Mulholland]

Apologies! Will do!

[michael.k...@gmx.at]

The FTP server login failed (530 Login authentication failed) for your user and password. Either you accidentally changed the credentials in your config, or the account expired or the provider changed something else that causes this error. Check, if you can log in using your credentials with another FTP-client, if that works, double check your credentials in weewx.conf. If that doesn't work, ask your provider for the reason you cannot login.

[Graham Eddy]

looks like their AI learnt from microsoft support messages - lots of words and no content

⊣GE⊢

[Monica Mulholland]

Thank you for that....where might I find the credentials....it has been 10 years since I set up all this and my memory is not that good anymore!

[Monica Mulholland]

Found it!

Status: Connecting to 43.245.53.39:21...
Status: Connection established, waiting for welcome message...
Status: Initializing TLS...
Status: Verifying certificate...
Status: TLS connection established.
Command: USER wilsonba
Response: 331 User wilsonba OK. Password required
Command: PASS **************
Response: 530 Login authentication failed
Error: Critical error: Could not connect to server

[Monica Mulholland]

"I hope this message finds you well.

I wanted to provide you with an update regarding the **weewxd** process on the server. We checked and confirmed that the **weewxd** process is currently running smoothly.

process log filtering weewxd:

[Sydney] [root@*********** log]# ps aux | grep weewxd
root 2593536 0.0 0.0 112808 976 pts/0 S+ 12:46 0:00 grep --color=auto weewxd

To further assist you in resolving any issues you may be facing, we kindly request the following information from you:

1. weewxd Version: Could you please confirm the version of **weewxd** that you are currently running on your website? This information will help us ensure compatibility and troubleshoot effectively.

2. Screenshot of Error Message: If possible, could you please provide us with a screenshot of any error message that appears when you attempt to restart **weewx** on your end? This will allow us to pinpoint the specific issue and provide you with tailored assistance."

Finally a somewhat sensible answer from the site host!!!!...though I am not sure how they have determined that weewx is running smoothly.

[vince]

That ps command and commentary they provided is so ridiculously wrong it is unbelievable.   Hopefully you're not letting them log into your pi3.

As michael.k said yesterday, your problem is that you have an incorrect setting in the FTP section of your weewx.conf file.  If it worked for years and does not work now, it is likely your password on the 'remote' server has changed.  You need to edit the correct username/password into weewx.conf and restart weewx and it should work.

Simplest test to figure it out is to try to ftp manually from a shell prompt on the pi and verify you have the correct remote host, username, and password.   Something changed on your server side if you didn't change anything on the pi.

[Monica Mulholland]

Yes! This is very obviously a server problem and not a weewx problem. See attached where I have tried to connect using Filezilla but with the same information!

[Monica Mulholland]

"Thank you for your response.

We sincerely apologize for any inconvenience this may have caused you. Please know that it is never our intention to cause any hassle, and we truly understand the urgency of this issue.

We already did a thorough investigation and checked on this issue, and we can confirm that the server is properly working fine and we do not see any issues with the server.

We also checked the logs, and there we found out that the error was coming from an authentication failure. Please refer to the logs below:

Jul 5 15:40:29 WeatherPi weewx [25601] ERROR weewx.reportengine: ftpgenerator: (1): caught exception '<class 'ftplib.error_perm'>': 530 Login authentication failed

530 Login authentication failed means that the username or password provided for the FTP connection is incorrect.

Let us know if you have further questions."

This is the latest response from the website host....does this make any sense? These are hardwired into weewx.conf...and have been so for 10 years...and worked without a problem?

If I use them in Filezilla, I also get the 503 error.

How to make sense of this?

[vince]

Seems pretty obvious that you are using the wrong username/password combination. I think several folks said that multiple times.

Change your password on their site. WRITE IT DOWN and edit it into weewx.conf to match.

[Monica Mulholland]

Yes, that would seem the logical conclusion...except that is the username and password that is hardwired into the weewx.conf and has not been changed by me in 10 years!

[Graham Eddy]

i suggest cut through the noise: just tell the ISP to change the ftp password to whatever it is you have in the weewx.conf now

⊣GE⊢

[Cameron D]

I have had occasions in recent years where sites have hardened policies and started rejecting perceived weak passwords, or switched user ID between a name and an email address - previously I could use either and then they stopped allowing one of them.
I am not sure I was always told about it beforehand.

To find out, I would need to use an interactive login (web-browser) to the management interface.

Some systems also allow different auth id/password between management and sftp.

[vince]

Monica what is past is past and it doesn't matter how long your old password worked. 

If you are getting the same denied error 'now' with weewx and filezilla it is 100% certain that you need to use your provider's procedure to get a new updated password for their server. Just do so please. Really.