• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Search results

  1. B

    Resolved Update broke FTP access

    Ok, so I found out, that IONOS moved our server to another data centre and changed the firewall rules. Activating 49152 65535 there, and it's working again. I'm sorry for my rant earlier, this time it was not the Plesk update breaking things. How do I set this to resolved?
  2. B

    Resolved Update broke FTP access

    Ok, the /etc/proftpd.d/55-passive-ports.conf is there, like in the article. So it should work. By exporting the firewall rules, I was also able to confirm, that this is set up properly. I'm just wondering, why you can't just read the rules.
  3. B

    Resolved Update broke FTP access

    Maybe I should add, that our deployment in this case is done with lftp. I have some progress. I set the connection mode in cyberduck to active and I can access the server. Now I read that passive mode is usually disabled: (Plesk for Linux) Configuring Passive FTP Mode Why did it work until now...
  4. B

    Resolved Update broke FTP access

    Tried this now without success: - Turned of Firewall - Turned of Web Application Firewall
  5. B

    Resolved Update broke FTP access

    Hi, our deployment via FTP stopped working. So I checked and we can't access the FTP from two different machines any more. It was working fine two weeks ago, today it's not working. I log in to Plesk and see an automatic update has been done. Why do I have problems and need multiple hours of...
Back
Top