Community
    • Categories
    • Recent
    • Popular
    • Users
    • Search
    • Register
    • Login

    i-doit update from 35 to 36 fails with permissions issues

    Scheduled Pinned Locked Moved Operating
    2 Posts 1 Posters 4 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P Offline
      Promenade1037
      last edited by

      When I attempt to update our i-doit Open installation from 35 to 36, I receive an error message that /var/www/html is not writable. However, I have run the "idoit-rights.sh set" script to ensure that everything is writable and have verified that the apache user has ownership of all files. When I attempt to look for new updates using the Updater screen, our environment reports "Error while connecting / cURL Error: 7," so I manually downloaded the idoit-open-36-updates.zip file and unzip it in the /var/www/html folder as specified in the KB article. After it is unzipped, I then run the "idoit-rights.sh" script to set the permissions. Below are the screenshots, but the update procedure will not progress once the errors are reported. Any help getting past this state would be appreciated. I have searched the KB articles, and have used the guidance in https://kb.i-doit.com/en/system-administration/troubleshooting/known-update-problems.html, including the "Files cannot be copied" guidance. There does not appear to be any hotfix for this issue.

      Environment:
      Rocky Linux 9.7 (RHEL clone)
      PHP 8.3.26
      MariaDB 10.11.10
      RAM: 4 GB

      Screenshot 2025-12-31 115008.png
      Screenshot 2025-12-31 115026.png
      Screenshot 2025-12-31 115057.png
      Screenshot 2025-12-31 115215.png
      Screenshot 2025-12-31 115256.png

      Thanks,
      James

      P 1 Reply Last reply Reply Quote 0
      • P Offline
        Promenade1037 @Promenade1037
        last edited by

        Answering my own question, I reviewed /var/log/messages and found the following entry: "SELinux is preventing /usr/sbin/php-fpm from write access on the directory /var/www/html." Once I disabled SELinux, the update was able to proceed as usual.

        James

        1 Reply Last reply Reply Quote 0
        • First post
          Last post