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

Bug - Interface not load #768

Closed
puimpsyc opened this issue Dec 22, 2022 · 12 comments
Closed

Bug - Interface not load #768

puimpsyc opened this issue Dec 22, 2022 · 12 comments

Comments

@puimpsyc
Copy link

Hi! , I installed everything, I access in 127.0.0.1:8000 but the interface does not load well.
Sin título

@github-actions
Copy link

👋 Hi @puimpsyc,
Issues is only for reporting a bug/feature request. Please read documentation before raising an issue https://rengine.wiki
For very limited support, questions, and discussions, please join reNgine Discord channel: https://discord.gg/azv6fzhNCE
Please include all the requested and relevant information when opening a bug report. Improper reports will be closed without any response.

@gearcapitan
Copy link

the same problem
imagen

@barbixxxa
Copy link

barbixxxa commented Dec 23, 2022

#769 (comment)

use pull request #767 please read pull request or other issue before opening the issue also #768

didnt work for me

I tried to clone the pull request you said, reinstaled everything and it was the same
I also tried to reinstall from previous commits (797d108 and f79503d) and it was the same
I tried downloading the release 1.3.4 and reinstalling it, but no lucky
Release 1.3.0 has the same behaviour
image

@paweloque
Copy link
Contributor

Did you find a solution for that? I have the same problem. It looks like the collectstatic is not executed during the build.

@zinwelzl
Copy link

same problem here, nothing helps

https://rengine.wiki/install/quick/

instalattion ok, but https://127.0.0.1/ nothing

0.0.0.0:8000 just white page

what is going on?
how to repair this?

docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
4d0fcf8d3c99 peterdavehello/tor-socks-proxy "/usr/bin/tor -f /et…" 4 minutes ago Up 4 minutes (healthy) 8853/udp, 9150/tcp rengine_tor_1
c672d3eadaa2 nginx:alpine "/docker-entrypoint.…" 4 minutes ago Restarting (1) 16 seconds ago rengine_proxy_1
3248a8272ccc docker.pkg.github.com/yogeshojha/rengine/rengine:latest "/usr/src/app/entryp…" 4 minutes ago Up 4 minutes 0.0.0.0:8000->8000/tcp, :::8000->8000/tcp rengine_web_1
b4d8530ce894 rengine_celery-beat "/usr/src/app/beat-e…" 4 minutes ago Up 4 minutes rengine_celery-beat_1
ca65633e8f35 rengine_celery "/usr/src/app/celery…" 4 minutes ago Up 4 minutes rengine_celery_1
92446d487abf redis:alpine "docker-entrypoint.s…" 22 minutes ago Up 4 minutes 6379/tcp rengine_redis_1
b681fbce55dd postgres:12.3-alpine "docker-entrypoint.s…" 22 minutes ago Up 4 minutes 0.0.0.0:5432->5432/tcp, :::5432->5432/tcp rengine_db_1

@blackpungas
Copy link

I had the same issue and try everything, couldnt solve it. i dont get why a 5k star repo have instalation issues.

@paweloque
Copy link
Contributor

@blackpungas I think that being upset at the creators is not the best of ideas here. We better try to figure out why this is not working instead of complaining. I'm trying to execute collectstatic and serve the results via the django app. The proxy might have some problems do to domain configuration or certificates. I don't have a working solution yet though

@paweloque
Copy link
Contributor

paweloque commented Dec 26, 2022

Please have a look at this issue (duplicate) #769 (comment)

@paweloque
Copy link
Contributor

you can either set the DEBUG=1 parameter to serve static files via Django or change the ssl_ecdh_curve nginx param to

ssl_ecdh_curve                                  secp384r1:X25519:prime256v1;

And properly set your domain in the .env file.
In my case this helped and I can properly start reNgine.

@gearcapitan
Copy link

you can either set the DEBUG=1 parameter to serve static files via Django or change the ssl_ecdh_curve nginx param to

ssl_ecdh_curve                                  secp384r1:X25519:prime256v1;

And properly set your domain in the .env file. In my case this helped and I can properly start reNgine.

Didn't work for me!.

imagen

@yogeshojha
Copy link
Owner

@yogeshojha
Copy link
Owner

Also, nginx issue has been fixed in v1.3.5

Thanks

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

No branches or pull requests

7 participants