[GH-ISSUE #150] "I agree" error doesn't display if you switch tabs #132

Closed
opened 2026-02-26 06:30:30 +03:00 by kerem · 3 comments
Owner

Originally created by @bdillahu on GitHub (May 25, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/150

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    Yes
  • Are you sure you're not using someone else's docker image?
    Yes
  • If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network?
    Yes

Describe the bug

  • A clear and concise description of what the bug is.
    When adding a new Proxy Host, if you choose a new SSL cert, then you need to click the "I Agree" check for Let's Encrypt. If you miss that, you get an error. If you have changed to another tab (say Advanced) before hitting save, there is no error and things just sit.

  • What version of Nginx Proxy Manager is reported on the login page?
    v2.0.13

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
    Hosts->Proxy Hosts->Add New Host
  2. Click on '....'
    Fill in valid info - choose to request new SSL cert
    Do NOT click "I agree"
  3. Scroll down to '....'
    Change tab to advanced
  4. See error
    Hit Save - no error given and things stop

Expected behavior
A clear and concise description of what you expected to happen.

Should see an error - maybe switch tabs back to SSL tab.

Screenshots
If applicable, add screenshots to help explain your problem.

Operating System

  • Please specify if using a Rpi, Mac, orchestration tool or any other setups that might affect the reproduction of this error.

Additional context
Add any other context about the problem here, docker version, browser version if applicable to the problem. Too much info is better than too little.

Originally created by @bdillahu on GitHub (May 25, 2019). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/150 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? Yes - Are you sure you're not using someone else's docker image? Yes - If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network? Yes **Describe the bug** - A clear and concise description of what the bug is. When adding a new Proxy Host, if you choose a new SSL cert, then you need to click the "I Agree" check for Let's Encrypt. If you miss that, you get an error. If you have changed to another tab (say Advanced) before hitting save, there is no error and things just sit. - What version of Nginx Proxy Manager is reported on the login page? v2.0.13 **To Reproduce** Steps to reproduce the behavior: 1. Go to '...' Hosts->Proxy Hosts->Add New Host 2. Click on '....' Fill in valid info - choose to request new SSL cert Do NOT click "I agree" 3. Scroll down to '....' Change tab to advanced 4. See error Hit Save - no error given and things stop **Expected behavior** A clear and concise description of what you expected to happen. Should see an error - maybe switch tabs back to SSL tab. **Screenshots** If applicable, add screenshots to help explain your problem. **Operating System** - Please specify if using a Rpi, Mac, orchestration tool or any other setups that might affect the reproduction of this error. **Additional context** Add any other context about the problem here, docker version, browser version if applicable to the problem. Too much info is better than too little.
kerem 2026-02-26 06:30:30 +03:00
  • closed this issue
  • added the
    stale
    bug
    labels
Author
Owner

@chaptergy commented on GitHub (May 10, 2021):

Unfortunately this happens everywhere with tabs, e.g. the port for proxy hosts as well

<!-- gh-comment-id:837408066 --> @chaptergy commented on GitHub (May 10, 2021): Unfortunately this happens everywhere with tabs, e.g. the port for proxy hosts as well
Author
Owner

@github-actions[bot] commented on GitHub (Apr 3, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:2033392841 --> @github-actions[bot] commented on GitHub (Apr 3, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@github-actions[bot] commented on GitHub (May 12, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:2870529176 --> @github-actions[bot] commented on GitHub (May 12, 2025): Issue was closed due to inactivity.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#132
No description provided.