Something went wrong! Please try again. #236
Comments
|
Tried this on a new VM and the containers do in fact now show, but they keep terminating:
|
|
Did you verify that you filled out all the information in the .env file correctly?
It took me a few attempts to get it all sorted Finally removing the mysql container to have it rebuild if you fiddled with it before that was all working like I did. A quick side note, the |
|
I am getting the exact same issue on a fresh install, get this in the nginx log EDIT: This only seems to be an issue with the prod, nonprod appears to work |
|
Hello everyone,
Also you can check my Running logs |
|
@idiosyncric Can you tell me if the .env file is filled correct way? |
|
I have a similar issue : X
|
|
@asenawritescode If you have a similar issue try to explain it, Except if it's the exact same issue. |
|
Anyway the server and frontend are running correctly, the issue is with the migration. 
|
It is exactly the same problem, works on local though. |
|
@abouolia Can you take a look on this issue, whatever info you need I more than happy to answer you. I can already tell you that we did follow the installation steps you asked about in this comment: Thank you! |
|
@asenawritescode @elbeicktalat I read the logs of the migration container, the error in that line |
|
@asenawritescode @elbeicktalat What the operating system and CPU architecture do you use? I want to duplicate the same exact environment. |
|
@asenawritescode @elbeicktalat I tried the docker compose setup on Ubuntu, Debian, CentOS and Redhat, I got no problem, I'm afraid you were run it on Windows (that would be my next trial). please let me know what is your OS? |
|
I am running docker on windows 10. PS.
|
|
@asenawritescode That was expected on Windows I should bring Windows machine to try out, if you mean the env vars, they are pre-configured you don't have to change them to get started. |
|
@abouolia Are you able to pin down the specific issue with the migration ? I actually don't understand what the underlying issue is. It would be helpful. |
|
Hi Fellas I think this issue is windows related as I was having trouble with it until I moved my install to linux debian 12 server and it worked like magic. to confirm this i also tried on Mac OS as will it was also working. |
|
Good coding everyone, You can install Docker on WSL by following next steps:
From now on you can follow the bitcapital docs. |
|
Of Course the issue causd by windows. I'm using: |
Everyone here who has an issue is using windows |
the issue is your mail config, should be smtp not smpt :) |
|
The issue has been fixed. #432 |
I've installed Bigcapital on a clean VM running Debian 11 w/
When I go to
http://<IP>, I get the following error message when completing the form to register for a new account:When I check what docker containers exist with
sudo docker psI get:Seems there are a few missing. As this is a clean install using the instructions exactly as presented on https://docs.bigcapital.ly/deployment/docker, I'm hoping someone has an idea as to what is going on here.
When I run
sudo docker ps -a | grep bigcapital-database_migration, nothing returns.When I run
docker volume rm bigcapital_prod_mysql, it returnsError: No such volume: bigcapital_prod_mysql.Something else I noticed is when the instructions mention: "Wait for all containers to be in running state, and then point your browser to http://:8000/ to access the application," BC doesn't respond on that port (no, my firewall isn't running). The only response I get is on port 80.
The text was updated successfully, but these errors were encountered: