Closed 1ubuntuuser closed 2 years ago
I have found the same result on a fresh install of debain 11. I carefully followed instructions here too. https://github.com/frappe/frappe_docker/blob/main/docs/setup-options.md
Hi, just checking if we are facing the same issues (again). What exactly are you trying to do? I was trying to setup ERPNext inside the docker container.
I was also getting errors when trying to access the site. I had to manually exec a command in the backend
container. Try this doc. The db-password can be found in the docker-compose.yaml
.
For me I had to run the following two commands to setup ERPNext (I still have some issues, so take this with a grain of salt)
❗️<site-name>
has to match the url you are trying to access.
docker-compose exec backend bench new-site <site-name> --mariadb-root-password <db-password> --admin-password <admin-password>
docker-compose exec backend bench --site <site-name> install-app erpnext
@defnotjonas
Tried
docker-compose exec backend bench new-site <site-name> --mariadb-root-password <db-password> --admin-password <admin-password> docker-compose exec backend bench --site <site-name> install-app erpnext
and
docker-compose -f compose.yaml \ -f overrides/compose.erpnext.yaml \ -f overrides/compose.mariadb.yaml \ -f overrides/compose.redis.yaml \ -f overrides/compose.https.yaml \ config > ~/gitops/docker-compose.yml
still 404 , nginx is running, I am trying to access from ip address , also when trying from server itself with wget localhost, wget mysite.localhost same 404
Hi, I can’t replicate your setup right now, tomorrow I can give more exact feedback. Just to try my most common mistake: What are you using for site-name
? It should be localhost
or mysite.localhost
for you.
Of course localhost and mysite.localhost have to resolve to the correct IP (nslookup mysite.localhost
)
Tried with both
With IP
docker-compose exec backend bench new-site ipaddress --mariadb-root-password 123 --admin-password 123 docker-compose exec backend bench --site ipaddress install-app erpnext
With localhost
docker-compose exec backend bench new-site localhost --mariadb-root-password 123 --admin-password 123 docker-compose exec backend bench --site localhost install-app erpnext
getting 404 only
Sorry, I just went over your comment and I missed something.
docker-compose -f compose.yaml \ -f overrides/compose.erpnext.yaml \ -f overrides/compose.mariadb.yaml \ -f overrides/compose.redis.yaml \ -f overrides/compose.https.yaml \ config > ~/gitops/docker-compose.yml
I believe you are missing an override for proxy or no proxy. I was assuming your 404 resulted from frappe when instead it probably results from the Traefik proxy infront.
Please provide the contents of your docker-compose.yaml
(censor passwords and urls).
Also maybe read #715. It includes instructions partly suitable for your setup.
@defnotjonas, I did try with proxy and noproxy. Same result.
@1ubuntuuser @pptyasar After some downtime, I think we are facing two different issues between the two of you. If this is the case it would probably be best to create a new issue for @pptyasar. I am fairly certain that both issues are not bugs, but rather configuration issues resulting from lacking documentation. The lack of documentation is possibly fixed by the future pull request #715.
@1ubuntuuser Your problem does not stem from a docker-compose.yaml related issue, as you can reach the container. I think your issue stems from a missing site inside your container. Have you tried setting up a site in your backend container? https://github.com/frappe/frappe_docker/issues/711#issuecomment-1072375119
If @pptyasar docker-compose.yaml
points to Traefik as the problem, we should move their part of the discussion to a new issue. Excuse the resulting confusion. I probably miscategorized the issue when referring @pptyasar here.
does not exist
if the 404 mentions site .... does not exist.
then it is displayed by Frappe framework when the site url you're trying to reach does not exist in sites directory. Create the site first.
I'll add screenshot of traefik 404 and frappe 404 in troubleshoot documention.
My goal has been to get a single erpNext domain online. @defnotjonas I think you may be right. As a new commer, I had to fish around a bit to try find the right documentation to use. I thought it was https://github.com/frappe/frappe_docker/blob/main/docs/setup-options.md. Based on what you are saying the steps in that documentation are not enough. I didn't realise I had to also run the docker exec commands. I'll give it a try.
FYI this is the path I took to find the documentation. https://erpnext.com > Get Started > Install Open Source > https://github.com/frappe/erpnext > https://github.com/frappe/frappe_docker > Read the Docs/setup options > wrong docs apparently
I spent 8 hours so far and haven't been able to get an admin panel, I know it's open-source, so I'm not complaining but I feel launching a docker-compose stack should take far less effort.
It might be good to make it easier, something like: https://erpnext.com > Get Started > [Install with Docker]|[Install with Bench] > Easy tutorial with all steps.
404 from traefik: This means traefik can't reach internal service
404 from frappe: This means site needs to be created (bench new-site ...
)
https://erpnext.com/ > Get Started > Install Open Source > https://github.com/frappe/erpnext > https://github.com/frappe/frappe_docker > Read the Docs/setup options > wrong docs apparently
We recently refactored It will take a quarter to stablize I think.
frappe_docker is all community work ONLY so if you wish you can contribute updating the documentation or wait for others to put it up.
If you want old setup which was as easy as docker-compose up -d
check the compat branch of this repo https://github.com/frappe/frappe_docker/tree/compat.
I approved refactor because it is optimized and better. I'm okay with refactoring other things and updating documentation that is what I felt progress is.
With respect to your path to land here, we can observe that ANY installation procedure is neglected and you're on your own anyway. There are forum posts like "22 easy steps to install ERPNext" popping up every time. Even now if you visit forum one of the first ten post will be related to installation.
Many "bash" veterans will tell you manual install works and it is easy. Same way "container" veterans will say same about containerized setup.
tried everything , its been more than 10 days , feeling tired :(
I won't be merging #715 unless 100% of community can use the documentation mentioned in it. All the installation problems I'm directing there.
I can make it work, it takes me less than 5 min. Contributors can make it work. People who don't talk here can make it work. but community can't.
even if you @pptyasar can't use it, I'll not merge it.
I've blocked the merge for now because wizard failed for one user after installation. I'll also block that merge unless all unique people from the community can't successfully install frappe docker. Any related or unrelated error needs to be fixed.
move discussion to PR.
I won't be merging #715 unless 100% of community can use the documentation mentioned in it. All the installation problems I'm directing there.
I can make it work, it takes me less than 5 min. Contributors can make it work. People who don't talk here can make it work. but community can't.
even if you @pptyasar can't use it, I'll not merge it.
I've blocked the merge for now because wizard failed for one user after installation. I'll also block that merge unless all unique people from the community can't successfully install frappe docker. Any related or unrelated error needs to be fixed.
move discussion to PR.
@revant To be honest, I feel it's hard to follow the new setup instructions even I did successfully set up a production site in 10 minutes before the refactor.
The new docs really need to be re-organized.
If any one landed here, you might have missed the 💡 You should setup --project-name option in docker-compose commands if you have non-standard project name.
part in the https://github.com/frappe/frappe_docker/blob/main/docs/site-operations.md document. So when you create new site for a non-standard project name, you need to run with
docker compose --project-name something exec backend bench new-site something.localhost --mariadb-root-password the-password --admin-password the-password
If any one landed here,
I landed here because I used the easy install script.
With respect to your path to land here, we can observe that ANY installation procedure is neglected
I would really like to follow an installation procedure, but I can’t find any.
Also, I could not find any system requirements. How much RAM do I need? CPU? Disk space?
Description of the issue
I've been following the instructions to setup a production docker env. For some reason, no matter what overrides I use, noproxy, proxy, HTTP whenever I connect to the server I get a 404. I checked out the default.conf for nginx and couldn't see anything out of the ordinary. Any ideas? https://github.com/frappe/frappe_docker/blob/main/docs/images-and-compose-files.md
Context information (for bug reports)
Latest version of docker and docker-compose running on ubunu.
Steps to reproduce the issue
docker-compose -f compose.yaml -f overrides/compose.erpnext.yaml -f overrides/compose.mariadb.yaml -f overrides/compose.redis.yaml -f overrides/compose.proxy.yaml config > ~/app/erpnext/docker-compose.yml
docker-compose --project-name xx -f ~/app/erpnext/docker-compose.yml up
Stacktrace / full error message if available