[GH-ISSUE #704] Stuck at Getting the certificate, please wait... #1705

Closed
opened 2026-02-27 12:12:44 +03:00 by kerem · 6 comments
Owner

Originally created by @FluffyDiscord on GitHub (Nov 6, 2024).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/704

Describe the bug
Nginx UI fails to send request to create SSL certificate if its run from Firefox.

To Reproduce
Steps to reproduce the behavior:

  1. Create new site with custom config
  2. Switch back from Advanced to Basic view
  3. Try generating SSL certificate
  4. Windows pops up and it gets stuck

Expected behavior
Certificate creates normally

Screenshots
image

Info (please complete the following information):

  • Server OS: OpenSuse Leap 15.6
  • Server Arch: x86
  • Nginx UI Version: 2.0.0-beta.39 (2) [Docker]
  • Your Browser: Firefox

Additional context
Works using Chrome.

Originally created by @FluffyDiscord on GitHub (Nov 6, 2024). Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/704 **Describe the bug** Nginx UI fails to send request to create SSL certificate if its run from Firefox. **To Reproduce** Steps to reproduce the behavior: 1. Create new site with custom config 3. Switch back from Advanced to Basic view 4. Try generating SSL certificate 5. Windows pops up and it gets stuck **Expected behavior** Certificate creates normally **Screenshots** ![image](https://github.com/user-attachments/assets/3008d5df-4428-4d0c-b070-02c8cf218b9a) **Info (please complete the following information):** - Server OS: OpenSuse Leap 15.6 - Server Arch: x86 - Nginx UI Version: 2.0.0-beta.39 (2) [Docker] - Your Browser: Firefox **Additional context** Works using Chrome.
kerem 2026-02-27 12:12:44 +03:00
Author
Owner

@0xJacky commented on GitHub (Nov 7, 2024):

Hi @FluffyDiscord, did you run Nginx UI behind a reverse proxy?

<!-- gh-comment-id:2461103407 --> @0xJacky commented on GitHub (Nov 7, 2024): Hi @FluffyDiscord, did you run Nginx UI behind a reverse proxy?
Author
Owner

@0xJacky commented on GitHub (Nov 7, 2024):

If so, please modify the configuration file to allow Nginx to handle WebSocket requests for Nginx UI.

server {
    listen          80;
    listen          [::]:80;

    server_name     <your_server_name>;
    rewrite ^(.*)$  https://$host$1 permanent;
}

map $http_upgrade $connection_upgrade {
    default upgrade;
    ''      close;
}

server {
    listen  443       ssl;
    listen  [::]:443  ssl;
    http2   on;

    server_name         <your_server_name>;

    ssl_certificate     /path/to/ssl_cert;
    ssl_certificate_key /path/to/ssl_cert_key;

    location / {
        proxy_set_header    Host                $host;
        proxy_set_header    X-Real-IP           $remote_addr;
        proxy_set_header    X-Forwarded-For     $proxy_add_x_forwarded_for;
        proxy_set_header    X-Forwarded-Proto   $scheme;
        proxy_http_version  1.1;
        proxy_set_header    Upgrade             $http_upgrade;
        proxy_set_header    Connection          $connection_upgrade;
        proxy_pass          http://127.0.0.1:9000/;
    }
}
<!-- gh-comment-id:2461105006 --> @0xJacky commented on GitHub (Nov 7, 2024): If so, please modify the configuration file to allow Nginx to handle WebSocket requests for Nginx UI. ``` server { listen 80; listen [::]:80; server_name <your_server_name>; rewrite ^(.*)$ https://$host$1 permanent; } map $http_upgrade $connection_upgrade { default upgrade; '' close; } server { listen 443 ssl; listen [::]:443 ssl; http2 on; server_name <your_server_name>; ssl_certificate /path/to/ssl_cert; ssl_certificate_key /path/to/ssl_cert_key; location / { proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $connection_upgrade; proxy_pass http://127.0.0.1:9000/; } } ```
Author
Owner

@FluffyDiscord commented on GitHub (Nov 7, 2024):

No, it's not run behind reverse proxy. Also I noticed that the error I sent in screenshot happens also on Chrome, but at random. Refreshing page helps.

<!-- gh-comment-id:2461475918 --> @FluffyDiscord commented on GitHub (Nov 7, 2024): No, it's not run behind reverse proxy. Also I noticed that the error I sent in screenshot happens also on Chrome, but at random. Refreshing page helps.
Author
Owner

@Hintay commented on GitHub (Nov 8, 2024):

Hello, can you provide the running logs of the nginx ui at the time of this issue?

<!-- gh-comment-id:2464259928 --> @Hintay commented on GitHub (Nov 8, 2024): Hello, can you provide the running logs of the nginx ui at the time of this issue?
Author
Owner

@FluffyDiscord commented on GitHub (Nov 8, 2024):

Hi, there is nothing to send. It's a cors issue as mentioned before. You can see the only error on the screenshot. The request was blocked by browser apparently, so nginx doesn't even see it

<!-- gh-comment-id:2464313213 --> @FluffyDiscord commented on GitHub (Nov 8, 2024): Hi, there is nothing to send. It's a cors issue as mentioned before. You can see the only error on the screenshot. The request was blocked by browser apparently, so nginx doesn't even see it
Author
Owner

@0xJacky commented on GitHub (Nov 16, 2024):

I will fix it later.

<!-- gh-comment-id:2480369765 --> @0xJacky commented on GitHub (Nov 16, 2024): I will fix it later.
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-ui#1705
No description provided.