• 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. E

    Errors after upgrade to 11.5.30

    Hi, I just upgraded the panel to 11.5.30 and I am getting this error message on panel homepage: New configuration files for the Apache web server were not created due to the errors in configuration templates: Template processing failed: file =...
  2. E

    byte-range support

    Hi, can some please tell me how to check if a Plesk server 11.0.9 Update #55 supports byte ranges? I am having problems serving a podcast on one of our sites. On some research I found Apple specifications for serving audio files, they say the server must have byte-range support Thanks
  3. E

    There is no IP address 67.23.xxx.yyy in the pool

    Come on parallels, I did not cause this problem, it was one of your updates. Not long ago I added and deleted a new client and domain and it worked. I am tired of changing ip addresses to shared everyday. Does upgrading to plesk 11 fix the problem? Thanks
  4. E

    There is no IP address 67.23.xxx.yyy in the pool

    Hi, I don't have any clients with pool id 0 so this is not the solution to my problem. I don't need to add any subscriptions right now, but I am planning an upgrade soon. Shall I wait until the problem is fixed? Why do ip addresses get reset from shared to dedicated every day?
  5. E

    There is no IP address 67.23.xxx.yyy in the pool

    the query resulted in 0 or empty. All domains have the correct ip address. I have several available ip addresses, but when I try to add a subscription I get the ip pool empty error. I could add a subscription if I set one of the available dedicated ip addresses to shared, but it gets reset to...
  6. E

    There is no IP address 67.23.xxx.yyy in the pool

    Thanks for the reply. Do you mean to say that all the customers that come up from this query: select distinct c.id, c.pname from clients c, domains d where d.cl_id = c.id and c.pool_id = 0; do have a problem?
  7. E

    There is no IP address 67.23.xxx.yyy in the pool

    I have the same issue of: It is impossible to create a subscription: IP pool is empty. This this is not true, I have several ip addresses, but the panel does not know they are available. I am able to add a new subscription if I change one of the ip addresses in the pool to shared, but it also...
  8. E

    IP pool is empty - after Upgrade 10.4.4

    I am now able to add new subscriptions if I set some of the dedicated ip addresses to shared. I would like to solve this, since it is not the default panel behavior. Someone please help
  9. E

    Added new IP to Plesk 11. Doesn't show up in new customer/subscription creation

    I have a pool of dedicated ip addresses for new subscriptions, but when I try to add new subscriptions, I don't see any of the available ips. As a work around, I set one of the ips to shared which allowed me to ad the subscription I needed. Has anybody been able to fix this problem?
  10. E

    IP pool is empty - after Upgrade 10.4.4

    Hi I have the same issue, but it happened after I changed changed the subscriber of one of the domains. Please help
  11. E

    Unable to load object of type IPAddress with id=2

    The one time I had this problem, I went to the database via phpmyadmin and deleted several table rows, one at at time until the error disappeared. I also had the problem after I changed the ip pool space to a new my data center assigned out of the blue
  12. E

    help: cannot access ftp (passive mode)

    Vincenzo, I added IPTABLES_MODULES="ip_conntrack_ftp" and restarted iptables, but nothing different happened. Passive FTP works fine with unsecured connections, but I am still having problems with TLS/SSL FTP connections. I get the error of not being able to go into passive mode.
  13. E

    help: cannot access ftp (passive mode)

    This is a dedicated server.
  14. E

    help: cannot access ftp (passive mode)

    This is what I have in iptables.config: IPTABLES_MODULES="ip_conntrack_netbios_ns" should the quotation marks be empty? Thanks for replying!
  15. E

    help: cannot access ftp (passive mode)

    RuedigerK, I wanted to let you know after stopping the iptables, I went to psa-firewall and modified one of the rules to get iptables to restart, and everything is now working with FTP-TLS as well. What do you think the problems was? iptables? Thanks a million for helping
  16. E

    help: cannot access ftp (passive mode)

    Hi, I just remembered I had configured proftpd with this kb: http://kb.parallels.com/en/2207 for TLS support. I also checked to see if the current version: ProFTPD Version 1.3.3e is compiled for mod_tls.c and it is. Something changed and I can't figure it out.
  17. E

    help: cannot access ftp (passive mode)

    It is now working with unsecured FTP, it still not working with FTP TLS/SSL. The weird thing is it was working until last update: 10.4.4 Update #47 Do iptables need to stay down? They will started next time xinetd starts Thanks so much for helping
  18. E

    help: cannot access ftp (passive mode)

    thanks for replying so fast. I did disable it like this: /etc/init.d/psa-firewall stop then checked for iptables like this: /etc/rc.d/init.d/iptables status and iptables were up. Anyway, I still can't get FTP passive to work on FTP active mode
  19. E

    help: cannot access ftp (passive mode)

    Hi Joseph, did you find a solution to your problem? If so, would you please post your solution?
  20. E

    TLS connect failed error from qmail

    I used to have that problem, but at some point I switched to postfix, and now even port 465 works correctly. My guess is that when I switched, new binaries without the problem were installed
Back
Top