-
Notifications
You must be signed in to change notification settings - Fork 371
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
APP_DEBUG is set to true while APP_ENV is not local #389
Comments
When you get the error telling you to refresh the page, you should check logs using `docker exec -it socioboard bash -c "cat /usr/socioboard/app/socioboard-web-php/storage/logs/laravel.log" to see what the error was. |
Logs seems to be empty.
|
What about the pm2 logs? |
bash-5.1# cat pm2.log |
|
yep. same.
|
That's not right, there are meant to be services running. Keep in mind you can't make too many changes once the container has been created. It was designed to set everything on first run. If you need to make changes, kill the containers(databases are stored in volumes so login etc. won't be affected) and redeploy. See |
Sure. At one of the places I saw an error stating that sequelize did not run. I will try to see if that error comes again and will share in this thread. |
bash-5.1# ls -lrt |
A complete error for pm2 logs
|
I fixed a sequelize error recently, are you using my fork? |
Yes this makes me think it is a database error. You'd be best off deleting everything, volumes, containers and data folder. Clone my fork and start over. |
I was picking it from the socioboard. Let me head over to your fork and try again. |
Ah that explains it. I've pushed fixes that haven't been merged yet. |
The error continues. this time the site doesnt even come up for some weird reason. for both 8000 and 8080 I find "This site can’t be reached" error.
|
See EDIT: Please read the ReadMe in full, the update changed a lot. |
I still have not been able to get running with docker. The manual installation seems to be a huge pain. I created a new AWS EC2 Amazon Linux instance and restarted the whole process. I am able to see the nginx home page but not able to view :8000/login or :8080/admin pages. Any suggestion on where the logs are located to view whats going wrong? I have tried searching in /var/www/log or /var/nginx/log but they seem to be empty. |
|
@krishnakanthpps When using Docker use my fork as fixes have not been merged yet. Please read |
Can you help me on what settings do I need to update so that I can see the installation's login and admin screens? I did not change the BASE_DOMAIN="mydomain.example". I am kind of lost here now. |
@krishnakanthpps I added NGINX as a reverse proxy so you can only reach the login from You need some sort of DNS resolver to point those addresses to the IP of the machine your SocioBoard is running on. See |
I used the docker installation on Amazon Linux EC2 instance.
While trying to login with a new user I am getting this error.
Initially it says there was an issue and please reload. When I do a refresh of the page while trying access /dashboard URL I get this error.
The text was updated successfully, but these errors were encountered: