Fix WAMP SSL Chain Issue
Budget: $250 – $750 USD
I run a WAMP stack (Apache + MySQL + PHP) on a Windows Server hosted in Azure. I have already installed a GoDaddy SSL certificate and the public website at
https://alcwebprod.airliftsites.com/ loads fine in every browser.
The problem only shows up over FTP: anyone connecting with FileZilla receives an “incomplete / bad certificate chain” warning. No complaints appear over HTTP or HTTPS, so the issue seems limited to the way the intermediate certificates are presented to the FTP service.
What I know so far
• Protocol with errors: FTP (FTPS) only
• Client that reports it: FileZilla
• Intermediate bundle from GoDaddy has NOT been installed on the server yet.
What I need
• Analyse the current certificate files on the Azure-hosted Windows VM.
• Correctly install and chain the GoDaddy intermediate certificates so that FileZilla (and any other FTP client) accepts the connection without warnings.
• Ensure the existing HTTPS site keeps working throughout the change.
You may work through Remote Desktop, Anydesk, or simply send me the exact steps and files I should place; whichever is quicker for you. I’ll test the fix right away in FileZilla—no “bad chain” message will mean the job is done.
https://alcwebprod.airliftsites.com/ loads fine in every browser.
The problem only shows up over FTP: anyone connecting with FileZilla receives an “incomplete / bad certificate chain” warning. No complaints appear over HTTP or HTTPS, so the issue seems limited to the way the intermediate certificates are presented to the FTP service.
What I know so far
• Protocol with errors: FTP (FTPS) only
• Client that reports it: FileZilla
• Intermediate bundle from GoDaddy has NOT been installed on the server yet.
What I need
• Analyse the current certificate files on the Azure-hosted Windows VM.
• Correctly install and chain the GoDaddy intermediate certificates so that FileZilla (and any other FTP client) accepts the connection without warnings.
• Ensure the existing HTTPS site keeps working throughout the change.
You may work through Remote Desktop, Anydesk, or simply send me the exact steps and files I should place; whichever is quicker for you. I’ll test the fix right away in FileZilla—no “bad chain” message will mean the job is done.