[ThatOneGuy]

I got it working by disabling the SSL simply by changing the target's setup from:

"ssl"    "try"

to

"ssl"    "none"

[DarkDeviL]

Originally Posted by beetlejuice just tried this: https://byet.host/ free ftp hosting. So it is not only nfo i guess.... again: (Peer certificate cannot be authenticated with known CA certificates).

Closest match I found for a valid hostname towards them is "ftp.byethost7.com".

This one is exactly like NFO, "self signed certificate" && "expired".

CA stands for Certificate Authority, and the error output above means that the certificate isn't certified by a proper certificate authority that your system trusts.

If they were doing the exact same towards their public website https://www.nfoservers.com and/or https://byet.host/ - then you would be seeing warning in your browser, similar to this one:

-> last-time-i-checked-this-certificate-expired.darkserv.net

Originally Posted by ThatOneGuy I've submitted a support ticket to NFO on the issue in hopes they will look into it, as that may affect a quite a number of users. Thanks for the information. If they are unwilling to update their certificates, I will have to go the alternate route of disabling the verification.

With certificate authorities like for example https://letsencrypt.org - there is no reasons for NFO and others not to use their certificates for such services as FTP servers.

There are already a billion (... well, many!) scripts available so far, that can automate the certificate renewals with LE.

Any decent FTP(S) client should also warn you just like the SM plugin does.

[beetlejuice]

Thank you arne for explaining all it makes things much more clear!

How did theoneguy got it working then?

so with "ssl" "none" thats it? I tried and (login denied)
Did you also add those 2 curl lines to ignore certificate in teasyftp.sp?

I apologize for my noobness!

And thank you all so much for helping out!

[beetlejuice]

OK Got progress. changed to 22 port with ssl none and seems to be connecting now i am getting (timeout has been reached) again....

[beetlejuice]

OK another update...nfo responded and said i have to have unmanaged server to have it setup to be able to use teasyftp. hope they fix that

[ThatOneGuy]

Originally Posted by beetlejuice OK Got progress. changed to 22 port with ssl none and seems to be connecting now i am getting (timeout has been reached) again....

Try port 21. This was my working setup (running on a VDS through NFO):

Spoiler

"RemoteTargets"
{
	"togscrimdemos"
	{
		"host"					"YOUR HOST"
		"port"					"21"
		"user"					"INSERT USER NAME"
		"password"				"INSERT USER PW"
		"path"					"/public/demos"
		"ssl"					"none"
		"CreateMissingDirs"		"1"	
	}
}

[Krushy]

Plugin is broken?

[tEasyFTP.smx] Failed uploading FILE.zip (Login denied).

PHP Code:

"RemoteTargets"
{
    "demoupload"
    {
        "host"        "XX.XX.XX.XX"
        "port"        "21"
        "user"        "demo"
        "password"    "PASSWORD"
        "path"        "/"
        "ssl"        "try"
        
        "CreateMissingDirs"    "1"        
    }
} 


[Krushy]

Have a question.
Do you think i must open port on my FTP target or somethink else?

[beetlejuice]

[tEasyFTP.smx] Failed uploading 1500513811.dem (Upload failed (at start/before it took off)).

everything is setup fine and it connects to my ftp (passes login) but then at start it fails....

Anyone knows solution to this?

[j1gg]

Its possible to change timeout time? Sometimes I have this error Timeout was reached