Announcement

Collapse
No announcement yet.

LetsEncrypt issues

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Hi khairil

    Thanks for posting, and I know on the previous RC, there was a small issue on symlink with LE for multiple CN

    I might suggest you open a support ticket with IW and let them have a look to see what's going wrong fully

    If you do open a support ticket, login to nodeworx remote assistance, turn on remote assistance, then complete the support ticket, and include this forum thread link as well.

    I would appreciate if you could update your post once it's been resolved to help others

    If you do open a support ticket, please leave your IW as is, with Apache running

    Lastly, I should have checked, but your server does meet the minimum requirements I trust, which I assume it does or IW should not have installed.

    Also, apologies, trying to view your pictures on a small mobile with my eyes is not ideal for me

    I hope that helps

    Many thanks

    John

    Comment


    • #17
      Hem, Generating with LE is success again, but whyyyy my httpd is always stopped???

      Recently I am trying install Comodo Trial certificate, and my httpd is not stopped.

      what wrong???

      Comment


      • #18
        Hi khairil

        At a guess, I would think the LE symlink is causing perms errors in httpd

        If you care to test my theory, create a LE cert, Apache should stop on your server, but then run the 2 commands I posted earlier, which should resolve perms issues, then restart Apache

        If Apache restarts, then it is likely to be a permission issue

        As I posted above, I would open a support ticket

        Lastly, is your IW running the release candidate, if not I would update IW software to release candidate channel, update IW if new update available and test again

        Many thanks

        John

        Comment


        • #19
          Originally posted by d2d4j View Post
          Hi khairil

          At a guess, I would think the LE symlink is causing perms errors in httpd

          If you care to test my theory, create a LE cert, Apache should stop on your server, but then run the 2 commands I posted earlier, which should resolve perms issues, then restart Apache

          If Apache restarts, then it is likely to be a permission issue

          As I posted above, I would open a support ticket

          Lastly, is your IW running the release candidate, if not I would update IW software to release candidate channel, update IW if new update available and test again

          Many thanks

          John
          Thank you for your reply John,

          I have been created Support Ticket (USK-460102)

          Originally posted by d2d4j View Post
          At a guess, I would think the LE symlink is causing perms errors in httpd

          If you care to test my theory, create a LE cert, Apache should stop on your server, but then run the 2 commands I posted earlier, which should resolve perms issues, then restart Apache

          If Apache restarts, then it is likely to be a permission issue
          You mean these command?
          ~iworx/bin/cvspermsfix.pex

          ~iworx/bin/varpermsfix.pex
          ok, I will try it now.

          My IW is running on Beta Channel.

          Comment


          • #20
            Its fine? No such file or directory

            [root@srv1iw ~]# ~iworx/bin/cvspermsfix.pex
            /usr/bin/find: ‘/usr/local/interworx/lib/htmlpurifier’: No such file or directory
            /usr/bin/find: ‘/usr/local/interworx/lib/htmlpurifier’: No such file or directory
            [root@srv1iw ~]# ~iworx/bin/varpermsfix.pex
            [root@srv1iw ~]# ~iworx/bin/varpermsfix.pex
            [root@srv1iw ~]#

            Comment

            Working...
            X