Hey Federica,
I am sorry that our previous response is not explained clearly enough, the reason why my colleague keeps complaining your FTP access is not working is:
1. At first, we can connect with your FTP server via the Filezilla program without issue
2. We suspect the issue happening if we connected with your FTP server after a few minutes then it shows the following response when we try to open another file and debug
Status: Waiting to retry...
Status: Connecting to 157.90.135.249:21...
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
3. You can check the following full logs and show that I can open the file successfully, but it show couldn't connect when I try to open another file, then I can't open anything from your FTP server even trying to reconnect.
Status: Connecting to 157.90.135.249:21...
Status: Connection established, waiting for welcome message...
Status: Initializing TLS...
Status: Verifying certificate...
Status: TLS connection established.
Status: Logged in
Status: Retrieving directory listing...
Status: Directory listing of "/" successful
Status: Retrieving directory listing of "/administrator/components/com_payplans"...
Status: Directory listing of "/administrator/components/com_payplans" successful
Status: Retrieving directory listing of "/administrator/components/com_payplans/includes"...
Status: Directory listing of "/administrator/components/com_payplans/includes" successful
Status: Connecting to 157.90.135.249:21...
Status: Connection established, waiting for welcome message...
Status: Initializing TLS...
Status: Verifying certificate...
Status: TLS connection established.
Status: Logged in
Status: Starting download of /administrator/components/com_payplans/includes/controller.php
Status: File transfer successful, transferred 4,324 bytes in 1 second
Status: Starting upload of C:\Users\Arlex\AppData\Local\Temp\fz3temp-2\controller.php
Status: File transfer successful, transferred 4,548 bytes in 1 second
Status: Disconnected from server
Status: Retrieving directory listing of "/components/com_payplans/includes"...
Status: Connecting to 157.90.135.249:21...
Command: CWD /components/com_payplans/includes
Error: Connection timed out after 20 seconds of inactivity
Error: Failed to retrieve directory listing
Status: Disconnected from server
Status: Connecting to 157.90.135.249:21...
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
Status: Disconnected from server
Status: Delaying connection for 5 seconds due to previously failed connection attempt...
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
Status: Waiting to retry...
Status: Delaying connection for 5 seconds due to previously failed connection attempt...
Status: Connecting to 157.90.135.249:21...
Status: Connecting to 157.90.135.249:21...
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
Status: Disconnected from server
Status: Delaying connection for 5 seconds due to previously failed connection attempt...
Status: Connecting to 157.90.135.249:21...
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
Status: Disconnected from server
Status: Connecting to 157.90.135.249:21...
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
Status: Waiting to retry...
Status: Connecting to 157.90.135.249:21...
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
In my conclusion, I suspect your FTP server there has set some limitations about being unable to open more than 1 file or only allowing certain IP address users to connect with your FTP server few minutes.
@weeblr:
No, that's not where the problem comes from. They do not understand the issue unfortunately. The screenshot above (https://monosnap.com/direct/ntekVvqbQCTYYphOAFVffQDF6ar5r4) does not mean there is any issue in 4SEF. It's a normal 404 Exception, nothing special about it, throwing a 404 is absolutely normal and expected and is not the sign of any bug or issue.
THIS is the problem, and this is what they need to reply to, if they want to help:
https://assets.weeblr.net/images/screenshots/weeblr-2022-10-03-13.03.20.png
Why is Payplans first going to the correct, working URL and then doing a redirect to another, wrong URL? Once they reply to that, they'(ll probably be able to fix the bug.
Please quote me, copy my reply word by word to them.
Best regards
Yannick Gaultier
weeblr.com / @weeblr
=================================================================
@weeblr:
I have understoof what they are doing and why it's not working in their particular use case. It's breaking because they are doing a redirect but without asking for an absolute URL and also because the URL is created on the fly (each checkout has its own URL, created and used right away). I think I can make a workaround for this and make it work in all cases, new URL and existing URLs, normal URL or URL used in a redirect.
I'll get back to you later today.
Best regards
Yannick Gaultier
weeblr.com / @weeblr
And we are sorry that we missed answering Yannick's question in the previous reply, perhaps you can do us a favor to pass my following message to Yannick?
This is how the Payplan route behavior when the user clicks a plan on the listing page (without activating the 4SEF extension and Joomla URL rewrite setting on the site):
--------------------------------------------------------------------
1. Navigate to this plan page
https://www.mantrayogacentre.com/index.php/login/acquista/video-lezioni-yoga.html (current menu structure screenshot:
https://monosnap.com/file/R0kn0hoOlKtH3DHZcwUObTZc229h4o )
2. Select this plan "Corso ansia e stress plan" and the plan URL will be shown like this
https://www.mantrayogacentre.com/index.php/login/acquista/plan.subscribe/53.html?tmpl=component
3. The controller there will validate whether this is a valid plan and check other things as well. Once the validation is done, the system will try to redirect to the checkout page on the fly, which is this URL (according to the current site menu structure)
https://www.mantrayogacentre.com/index.php/login/acquista/checkout/8O56WJCMMDRY.html?tmpl=component, and the page load pretty fine.
If activate the 4SEF extension and Joomla URL rewrite setting:
--------------------------------------------------------------------
1. Navigate to this plan page
https://www.mantrayogacentre.com/acquista/1.html
2. Navigate to this plan page
https://www.mantrayogacentre.com/acquista/plan.subscribe/53.html?tmpl=component
3. Once the validation part is done, the system will pass this non-sef URL
index.php?option=com_payplans&view=checkout&invoice_key=xxxx&tmpl=component&Itemid=447 to the
JRoute, this is the SEF URL it return
login/acquista/checkout/8o56wjcmmdr6.html?tmpl=component
4. Then somehow the redirection URL become this
https://www.mantrayogacentre.com/acquista/plan.subscribe/login/acquista/checkout/8o56wjcmmdrk.html?tmpl=component so causing this 404 page.
Let us know if you would like to know anything else in the Payplans route process.
By the way, I would like to know 4SEF extension is it all the functionality same as the Sh404sef extension?