Skip to main content

New Nginx Manager and Certificate Errors

Comments

6 comments

  • cPRex Jurassic Moderator
    Hey there! I haven't heard about this just yet on my end, so for such a new feature a ticket might be best so we can investigate that directly on the system.
    0
  • jhawkins003
    Hey there! I haven't heard about this just yet on my end, so for such a new feature a ticket might be best so we can investigate that directly on the system.

    Will do! A ticket has just been submitted and I'll post back to the thread with any updates that might be helpful to others.
    0
  • cPRex Jurassic Moderator
    Could you post the number here so I can follow along on my end?
    0
  • jhawkins003
    Could you post the number here so I can follow along on my end?

    Sure! It is #94317166
    0
  • cPRex Jurassic Moderator
    Thanks - I'm following along with that on my end now as well :D
    0
  • jhawkins003
    We found a solution! An account that started with the letter "a" had a configuration bug. From the ticket - with 'alpha' substituted for the actual user ID: [QUOTE] ...There was an empty line in the alpha user's /var/cpanel/users/alpha file: DNS1= Removing this and rebuilding the /etc/userdomains and /etc/userdatadomains resolved the issue, and the EA-Nginx configurations rebuilt.
    Since the error occurred on the first domain Nginx tried to parse, none of the subsequent domains were properly handled by the Nginx config tool. When we manually toggled every domain, they were configured individually - which is why that work-around functioned for us. So a few final thoughts on this experience:
    • cPanel support was professional and excellent as always - if a bit on the slow side - but this was not an urgent issue, so no objections :)
    • Nginx Manager reported an error to us when it attempted to configure itself but did not provide output as to what the error actually was. If we had known it was related to the 'alpha' account, we probably would have tried re-provisioning that account which likely would have built a clean configuration for it and solved the Nginx Manager issue.
    • A single account experiencing a bug seems like something the Nginx Manager configurator should error trap for so that all subsequent domains it attempts to manage don't break.
    0

Please sign in to leave a comment.