Page 2 of 2
Re: Problem with Build 3220 Upgrade
Posted: Fri 06 Jan 2023 11:40 am
by broadstairs
apple8 wrote: ↑Fri 06 Jan 2023 11:05 am
Ok, how do I do that. I had a look in cpanel but don't know where to find FTP server logs.
On my hosting site I can view the logs by using the file manager in cpanel and in that there is a logs directory which contains the FTP logs in gzip format for each month. This also shows when I FTP into my main site and can then download the relevant gzip file to decompress and view.
Stuart
Re: Problem with Build 3220 Upgrade
Posted: Fri 06 Jan 2023 12:40 pm
by apple8
Thanks Stuart, found the file.
Added part of the file for when there was errors I believe. I can see there is a difference but don't know what it means.
I have also asked my host provider why it works with a ftp ip address and not with host name and waiting their response.
Re: Problem with Build 3220 Upgrade
Posted: Fri 06 Jan 2023 7:29 pm
by apple8
I received a reply from the host provider:
“That could be an issue with your ISP flapping between IPv4 and IPv6 as blazingcomet.com has both.
Using the IP address forces it to load to that IP which is IPv4.”
Now, if that is the case can that be fixed to IPV4 and if so where?
Re: Problem with Build 3220 Upgrade
Posted: Mon 09 Jan 2023 3:15 am
by apple8
Just to close out this thread.
The original problem of latest version not working for me was fixed by checking ignore certificate errors. Using host name instead of IP address to sort out the certificate errors caused another problem of data randomly being sent by IPv6 instead IPv4. I managed to get that working by disabling IPv6 on the wifi dongle. However that didn’t resolve the certificate errors and the IPv6 workaround I thought could lead to other issues later.
I realised that I had have gone down a rabbit hole and have decided the best way out is to stick with what works reliably. Build 3191 worked well with certificate error ignored built in with an FTP IP address and build 3220 with the ignore certificate errors option checked gives me the same thing.
At least I am running the latest version.