Getting This Puppy Up and Running

craigbass76 · December 21, 2020, 2:28pm

I just left a career in tech to help keep my in-laws’ lumber business in the family. While my eventual plan is to be paying support fees and letting someone else manage the migration, implementation, and training, and to have either an onsite server or some sort of local/cloud hybrid setup, for now I’m just trying to install on a headless Ubuntu install running in Virtualbox.

But the daemons don’t start at boot. I can manually start metasfresh_server.service and metasfresh-webui-api.service, but not metasfresh-material-dispo.service.

And even when I do start things manually, metasfresh_server.service goes belly up after a while (I haven’t figured out how long yet).

Postgres appears to be fine, I didn’t get any errors running the install script. When I fire up the server, I see all of the launch stuff fly by, and this at the end of my /opt/metasfresh/log/metasfresh.2020-12-21.log:

2020-12-21 09:15:02.300  INFO 8780 --- [main] de.metas.ServerBoot                      : Metasfresh Server started in 2.425 min

http://192.168.15.136/metasfresh/ is just a blank screen though.

alexbrugere · December 21, 2020, 5:58pm

There will be no help from the Metasfresh community. Think about that - if you are customer then there is no problem to pay. If you are going to be the developer then successful ignition of the project by yourself will prove your worth.

So - I am trying my best and hope that there can be some outside community as well.

metasnw · December 22, 2020, 3:16pm

hi @craigbass76
we recommend to use the docker setup and follow this instructions.
https://docs.metasfresh.org/installation_collection/EN/How_do_I_setup_the_metasfresh_stack_using_Docker.html

Your problem indicates that config.js might not be setup properly.

If you search in this forum you will find your are not the only one and there are numerous describing how to solve it.

Here some ideas where to start:

github.com/metasfresh/metasfresh-docker

White page solution / Weiße Seite Lösung (reverse proxy nginx caddy)

opened 08:23PM - 29 Oct 20 UTC

sutidor

### Is this a bug or feature request? Bug ### What is the current behavior? … When using a (nginx) reverse proxy and passing WEBAPI_URL=https://metasfresh.domain.tld through docker-compose.yml, start_webui.sh replaces https to http and thus provokes a mixed content issue. File in question: https://github.com/metasfresh/metasfresh-docker/blob/master/docker-src/webui/sources/start_webui.sh after else, line `sed -i 's/\https\b/http/g' /opt/metasfresh-webui-frontend/dist/config.js` ``` #!/bin/bash if [[ ! -z $WEBAPI_URL ]]; then sed -i 's,http\:\/\/MYDOCKERHOST\:PORT,'$WEBAPI_URL',g' /opt/metasfresh-webui-frontend/dist/config.js fi if [[ -f "/etc/apache2/certs/fullchain.pem" ]] && [[ -f "/etc/apache2/certs/privkey.pem" ]]; then sed -i 's/\bhttp\b/https/g' /opt/metasfresh-webui-frontend/dist/config.js a2ensite metasfresh_webui_ssl.conf echo "[METASFRESH] Activated SSL!" else sed -i 's/\https\b/http/g' /opt/metasfresh-webui-frontend/dist/config.js a2ensite metasfresh_webui.conf a2dissite metasfresh_webui_ssl.conf echo "[METASFRESH] Runnning Non-SSL!" fi ``` ### Which are the steps to reproduce? Run metasfresh docker using the example docker-compose file without certificates and then reverse proxy it. ### What is the expected or desired behavior? Assume that the input in WEBAPI_URL is correct including the protocol and write it as is into the config.js file. Alternative: Provide an option for reverse proxy. ### Hotfix bash into your container `docker exec -it metasfresh_docker_webui_1 /bin/bash` install editor nano, vi.. `apt-get install nano` edit files `nano start_webui.sh` comment out the line like so `#sed -i 's/\https\b/http/g' /opt/metasfresh-webui-frontend/dist/config.js` or remove it ctrl / strg+x, y to exit nano `nano /opt/metasfresh-webui-frontend/dist/config.js` replace http with https again ``` API_URL: 'https://metasfresh.domain.tld/rest/api', WS_URL: 'https://metasfresh.domain.tld/stomp' ``` (you can also add the ports if you have a different one like `https://metasfresh.domain.tld:8443`) ctrl / strg+x, y to exit nano you dont need to restart anything, because the config is read as the site is accessed. Changing the start script start_webui.sh makes sure it stays that way even after restarting. ### Hotfix 2 I created a start_webui.sh in the sources folder path/metasfresh-docker/webui/sources/ with the line `#sed -i 's/\https\b/http/g' /opt/metasfresh-webui-frontend/dist/config.js` and changed the Dockerfile in path/metasfresh-docker/webui/ as follows: after `COPY sources/configs/config.js /opt/metasfresh-webui-frontend/dist/` add 2 lines: ``` COPY sources/start_webui.sh / RUN ["chmod", "+x", "start_webui.sh"] ```

Hope that helps.

cheers,
norbert