Certificate Error when connecting by FTP

Discussion in 'Free Hosting' started by rednoise, Jan 12, 2020.

Thread Status:
Not open for further replies.
  1. rednoise

    rednoise New Member

    Messages:
    21
    Likes Received:
    1
    Trophy Points:
    3
    When I FTP to my profile by FTP, Filezilla throws up the error message, "The server's certificate is unknown. Please carefully examine the certificate to make sure the server can be trusted. Details - Valid from: 10/7/2019 8:00:00 PM, Valid to: 1/6/2020 6:59:59 PM - Certificate expired!; Hostname does not match certificate"

    I assume this is a side-effect of the migration. Are the admins aware of this? Is there anything I should do to mitigate this?
     
    Last edited: Jan 12, 2020
  2. Anna

    Anna I am just me Staff Member

    Messages:
    10,472
    Likes Received:
    446
    Trophy Points:
    83
    Given that your message say that the hostname doesn't match the certificate, what are you using as host?
     
  3. rednoise

    rednoise New Member

    Messages:
    21
    Likes Received:
    1
    Trophy Points:
    3
    ftp.rednoise.x10host.com , which is what my original setup instructions specified, and what has been working for a long time. Is this not correct?

    I may not have been clear - I can acknowledge the error and proceed with my FTP session, although the error message pops up again frequently, especially when I change directory.
     
  4. rednoise

    rednoise New Member

    Messages:
    21
    Likes Received:
    1
    Trophy Points:
    3
    As a test, I tried changing my hostname to rednoise.x10host.com . I can still FTP to my profile, but I still get the same error message about the expired certificate.
     
  5. Anna

    Anna I am just me Staff Member

    Messages:
    10,472
    Likes Received:
    446
    Trophy Points:
    83
    Only the server address itself will have a full certificate, in your case that would mean using x13.x10hosting.com as host, the individual domains that belong to users does not have ssl support.
     
  6. rednoise

    rednoise New Member

    Messages:
    21
    Likes Received:
    1
    Trophy Points:
    3
    OK, that makes some sense. My host name does not match the certificate. However, the other part of the error message mentions that this specific certificate expired on 1/6/2020 6:50:59 PM. Is that significant?

    I have always had Filezilla use the setting "Use explicit FTP over TLS if available" and have never seen this error message. Has the migration changed something that triggered this? Does this mean that I should use insecure plain FTP?

    ftp2.png
     
  7. Anna

    Anna I am just me Staff Member

    Messages:
    10,472
    Likes Received:
    446
    Trophy Points:
    83
    The certificate for x13 should not be a cpanel issued one as cpanel is not in use, so it is odd that you get that as issuer, unless it is somehow cached for your domain since earlier.

    The certificate that is present on the login page for DirectAdmin is issued by let's encrypt, which would logically be the same for ftp. What happens if you use x13.x10hosting.com as the host?
     
  8. butter14

    butter14 Member

    Messages:
    51
    Likes Received:
    2
    Trophy Points:
    8
    FTP over TLS never worked for me, it has always been the insecure plain FTP
     
  9. rednoise

    rednoise New Member

    Messages:
    21
    Likes Received:
    1
    Trophy Points:
    3

    Changing the host to x13.x10hosting.com works for me. When I first log on Filezilla presents me with this:

    ftp3.png

    After I accept the certificate I can log on with no more errors and my user user ID forwards me to my profile. This is how most FTP servers I've used work.

    Your solution works, but it contradicts the official setup instructions at https://x10hosting.com/support/guides/uploading-files . I hope that will be reconciled soon to avoid other people's confusion.

    Thanks for your help.
     
    Last edited: Jan 17, 2020
  10. rednoise

    rednoise New Member

    Messages:
    21
    Likes Received:
    1
    Trophy Points:
    3

    Filezilla has been set to "Use explicit FTP over TLS if available," which I had assumed meant to try TLS first and if that didn't work, to fall back to plain FTP. I don't remember now noticing whether my TLS connection was accepted or not, but it is now:

    Status: Resolving address of x13.x10hosting.com
    Status: Connecting to 198.91.81.13:21...
    Status: Connection established, waiting for welcome message...
    Status: Initializing TLS...
    Status: Verifying certificate...
    Status: TLS connection established.
    Status: Logged in
     
Thread Status:
Not open for further replies.

Share This Page