That is outside of my skill set.
Michael
Ben Hamilton (Ben Bradshaw) wrote on 2/12/21 12:21 PM:
Can you recompile curl with ftpes support?
Sent from my iPhone
On Feb 12, 2021, at 2:15 PM, wa7skg wrote:
I finally found the answer, but it doesn't help.
Supposedly, to use FTP over TLS in
Can you recompile curl with ftpes support?
Sent from my iPhone
> On Feb 12, 2021, at 2:15 PM, wa7skg wrote:
>
> I finally found the answer, but it doesn't help.
>
> Supposedly, to use FTP over TLS in EXPLICIT mode, you use ftpes instead of
> ftps. However, that kicks back with
>
> curl:
I finally found the answer, but it doesn't help.
Supposedly, to use FTP over TLS in EXPLICIT mode, you use ftpes instead
of ftps. However, that kicks back with
curl: (1) Protocol ftpes not supported or disabled in libcurl
So, I guess we're either going to have to do it manually in Filezilla
On 2/11/21 21:54, wa7skg wrote:
>
> Sorry, no joy.
>
> I can't get RDCatch to work for me over SSH right now.
>
> I'm trying this initially using curl from cli.
>
> curl -u u...@host.com:password ftps://hostname.com/path/program.mp3
>
> I get the error
>
> curl: (7) Failed connect to
On 2/11/21 17:44, wa7skg wrote:
>
> I think I found my problem. There are two types of FTP over TLS.
> Explicit uses port 21 while implicit uses port 990. Apparently
> RDCatch/curl uses implicit over port 990, which the host does not
> accept. In Filezilla, I have an option to select implicit or
Sorry, no joy.
I can't get RDCatch to work for me over SSH right now.
I'm trying this initially using curl from cli.
curl -u u...@host.com:password ftps://hostname.com/path/program.mp3
I get the error
curl: (7) Failed connect to hostname.com:990; Connection timed out
when I try normally.
I think I found my problem. There are two types of FTP over TLS.
Explicit uses port 21 while implicit uses port 990. Apparently
RDCatch/curl uses implicit over port 990, which the host does not
accept. In Filezilla, I have an option to select implicit or explicit.
Is there any way to specify
