Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[marjohn56]

Yes, the programmers favourite error... do it a lot myself. 

[broadstairs]

Thanks Eric, regarding the delete older than I changed the value without restarting DSLStats if that makes a difference.

Stuart

[roseway]

Stuart: Do you recall exactly what the age of the deleted snapshots was? Did it correspond with the setting you had before you changed it?

[broadstairs]

Yes I think so I'm pretty sure it was 10 days. It is still set to 60 days but today deleted the 19th May snapshots which would correspond to older than 10 days.

Stuart

[roseway]

I think it may be the case that the old setting is retained until you restart DSLstats. I'll test this on my own system, but it obviously shouldn't be necessary to restart.

[g3uiss]

Eric

I can confirm FTPS is working fine on my setup. However, it only works on P21 not P990. I thinking its falling back to explicit mode. (FTP over SSL/TLS explicit encryption)

I'm not sure how significant this is really.

Thanks for adding the FTPS, I can do everything I want to. Unfortunately at the moment I haven't worked out how to enable the Server 2016 that my host uses to parse .PHP files  Then I can try your scripts

Thanks Tony

[roseway]

Tony,

I've looked into this a bit more, and the curl --ssl option which I'm using at present does indeed specify explicit mode with fallback to port 21. There is an alternative which I could use: instead of --ssl I can specify the FTPS protocol in the URL by adding ftps:// instead of ftp:// in front of the domain name. This sets up implicit mode, but this mode does seem to be deprecated. So I suspect that the present situation is the preferred way to do it, but I would welcome your thoughts.

PS: One option which might be successful in your case would be to leave the port number blank. This causes curl to ask the server what port to use (passive mode). I have no idea if this will work, but it's easy to test.

[g3uiss]

Tony,

I've looked into this a bit more, and the curl --ssl option which I'm using at present does indeed specify explicit mode with fallback to port 21. There is an alternative which I could use: instead of --ssl I can specify the FTPS protocol in the URL by adding ftps:// instead of ftp:// in front of the domain name. This sets up implicit mode, but this mode does seem to be deprecated. So I suspect that the present situation is the preferred way to do it, but I would welcome your thoughts.

PS: One option which might be successful in your case would be to leave the port number blank. This causes curl to ask the server what port to use (passive mode). I have no idea if this will work, but it's easy to test.

Eric. Thanks. Don’t spend too much thought time on it. As it works in explicit mode on port 21 it’s fine for my purpose. I can’t see any major security issue. I will try leaving the port space blank to see if it works, I suspect it will.

Thanks for taking the time to look at it. Your work is so great for the community.

[g3uiss]

Eric. Thanks. Don’t spend too much thought time on it. As it works in explicit mode on port 21 it’s fine for my purpose. I can’t see any major security issue. I will try leaving the port space blank to see if it works, I suspect it will.

Thanks for taking the time to look at it. Your work is so great for the community.

Yes it did, but put 21 back in the port box. I’ve left it at 21 with FTPS selected.

Thanks

Tony