Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Huly instance, can't sign up "Unknown error: Failed to fetch" #21

Open
flotpg opened this issue Jul 22, 2024 · 11 comments · May be fixed by #36
Open

New Huly instance, can't sign up "Unknown error: Failed to fetch" #21

flotpg opened this issue Jul 22, 2024 · 11 comments · May be fixed by #36

Comments

@flotpg
Copy link

flotpg commented Jul 22, 2024

Hi,

I just started a new Huly instance, can't sign up "Unknown error: Failed to fetch".
CleanShot 2024-07-22 at 11 03 09@2x

Any hints what I can check?
Many thanks and best regards, Flo.

@debpalash
Copy link

Same here. on debian 12.6

Accounts Api returns ip:3000 = 500 Internal Server Error from front end just after fresh spawn.

@chen5293
Copy link

fail
I also encountered the same problem

@felipegoulart
Copy link

I had the same problem.

When running the setup script on my personal PC, I used localhost as the IP address, and that resolved the issue.

./setup.sh localhost

@flotpg
Copy link
Author

flotpg commented Aug 7, 2024

I had the same problem.

When running the setup script on my personal PC, I used localhost as the IP address, and that resolved the issue.

./setup.sh localhost

Didn't solve it for me...

@PhieuDieuVoCuc
Copy link

PhieuDieuVoCuc commented Aug 8, 2024

I observe with the browser dev-tool, and if there are any connection errors for the port in the console tab, I open that port (on the firewall) (for me, it’s 3000 and 3333) with a public IP or an IP that can be accessed from other machines (if not localhost).

@chen5293
Copy link

chen5293 commented Aug 8, 2024

You can try to add port 3000 to the network
His reverse proxy was not set up. I spent a long time troubleshooting.

@debpalash
Copy link

debpalash commented Aug 9, 2024

You can try to add port 3000 to the network His reverse proxy was not set up. I spent a long time troubleshooting.

hi, did you manage to get it working?

@chen5293
Copy link

You can try to add port 3000 to the network His reverse proxy was not set up. I spent a long time troubleshooting.

hi, did you manage to get it working?

Yes, I released a lot of ports on the server side

@ALOVEROFRAIN
Copy link

You can try to add port 3000 to the network His reverse proxy was not set up. I spent a long time troubleshooting.

hi, did you manage to get it working?

Yes, I released a lot of ports on the server side

hi, could you please show me the file "nginx.conf"

@emreggoktepe
Copy link

emreggoktepe commented Aug 27, 2024

Hi,

I'm encountering a persistent error while trying to redirect HTTPS traffic (port 443) to my application listening on port 8087 in Nginx. Despite having a functioning configuration for HTTP (port 80), the HTTPS configuration consistently fails. I've attached both configurations for your review.

Not Working conf;

server {
    listen                  443 ssl http2;
    listen                  [::]:443 ssl http2;
    server_name huly.domain.com;
    
    ssl_certificate     /etc/nginx/ssl/fullchain.pem;
    ssl_certificate_key /etc/nginx/ssl/privkey.key;

    access_log             /var/log/nginx/huly.domain.com-access.log;
    error_log              /var/log/nginx/huly.domain.com-error.log info;

    location / {
        proxy_pass http://localhost:8087;
        include proxy_params;
    }
}

server {
    listen 80;
    listen [::]:80;
    server_name huly.domain.com;

    location / {
        return 301 https://huly.domain.com$request_uri;
    }
}

Working conf;

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

    server_name huly.domain.com;

    location / {
        proxy_pass http://localhost:8087;
        include proxy_params;
    }
}

@egavrilov
Copy link

I would appreciate if you could test nginx config from this PR to be sure I'm not missing anything #32

@veryCrunchy veryCrunchy linked a pull request Sep 21, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants