Hi @Roysen,
Yesterday was unfortunately too busy for me to tend to this matter, but I could merge and publish @Marenz’s fix just now. See announcement below:
Yes. Briefly, the procedure should be as follows:
- Uninstall the rock-on
- Click on the “Update” button in the top right corner of the Rock-ons page to refresh the list of available rock-ons and refresh their definition. This will ensure you have the rock-on definition that include the fix.
- Re-install the rock-on.
Depending on the rock-on, you might also need to remove the contents of the share you used as the config share for Nginx-Proxy-Manager (either by deleting the files from the command line, or deleting and re-creating the share). I’m not familiar with how this rock-on writes its config, but it would ensure there’s no remnants of the previous (failed) attempts at starting this rock-on; something to keep in mind if you still encounter problems starting it.
Let us know how it goes!