Getting a Blank white page after doing the docker setup in centos 7

Sai_Kumar_Dasari · October 10, 2020, 1:39pm

Hi Team,

I tried setting up the metasfresh application in our environment on Centos 7 VM. The docker configuration and setup went without any errors. But when I am trying to access through Web it is giving me blank white page. Below is the docker-compose file I used.

docker-compose.yml

docker-compose.yml

db:
  build: db
  restart: always
  volumes:
    - ./volumes/db/data:/var/lib/postgresql/data
    - ./volumes/db/log:/var/log/postgresql
  environment:
    - METASFRESH_USERNAME=metasfresh
    - METASFRESH_PASSWORD=metasfresh
    - METASFRESH_DBNAME=metasfresh
    - DB_SYSPASS=System
    - POSTGRES_PASSWORD=ip2LmNzXX8p8iXg9lZTWEJ9524kQDbXFudB7LR03T-xK9fLweX3TLMkA2AYcEiaS
app:
  build: app
  hostname: app
  links:
    - db:db
    - rabbitmq:rabbitmq
    - search:search
  expose:
    - “8282”
    - “61616”
    - “8788”
  restart: always
  volumes:
    - ./volumes/app/log:/opt/metasfresh/log:rw
    - ./volumes/app/heapdump:/opt/metasfresh/heapdump:rw
  environment:
    - METASFRESH_HOME=/opt/metasfresh
webapi:
  build: webapi
  links:
    - app:app
    - db:db
    - rabbitmq:rabbitmq
    - search:search
  expose:
    - “8789”
    # to access the webui-api directly
    #(eg. for debugging or connecting your app to the metasfresh api)
    #uncomment following port:
  ports:
    - “9093:8080”
  restart: always
  volumes:
    - ./volumes/webapi/log:/opt/metasfresh-webui-api/log:rw
    - ./volumes/webapi/heapdump:/opt/metasfresh-webui-api/heapdump:rw
  webui:
  build: webui
  links:
    - webapi:webapi
  ports:
    - “9091:80”
    - “9092:443”
  restart: always
  #uncomment and set to URL where metasfresh will be available from browsers
  environment:
    - WEBAPI_URL=http://metasfresh:9093
  rabbitmq:
  build: rabbitmq
  expose:
    - “5672”
  restart: always
  volumes:
    - ./volumes/rabbitmq/log:/var/log/rabbitmq/log
  environment:
    RABBITMQ_DEFAULT_USER: “metasfresh”
    RABBITMQ_DEFAULT_PASS: “metasfresh”
    RABBITMQ_DEFAULT_VHOST: “/”
  search:
  build: search
  ulimits:
    memlock:
      soft: -1
      hard: -1
    nofile:
      soft: 65536
      hard: 65536
  cap_add:
    - IPC_LOCK
  #to access the search api directly
  #(e.g. if you did docker-compose up search to have the deachboard with your loc ally running metasfresh services)
  uncomment following ports:
  ports:
    - “9200:9200”
    - “9300:9300”
  volumes:
    - ./volumes/search/data:/usr/share/elasticsearch/data
  environment:
    - “ES_JAVA_OPTS=-Xms128M -Xmx256m”
  restart: always

There are no errors or warnings.

This is the result of the docker compose up and container list:

Can anyone please help me out on this.

Admin-Edit:
I changed formatting of your docker-compose.yml content. So it’s easier to identify possible issues.

In the Editor, you can just mark the text that shall preserve formatting (especially yml files) and select the ‘Preformatted text’ button (</> , or [ctrl]+[shift]+[c] )
Cheers.

TKlerx · October 19, 2020, 8:57pm

Hi Sai,

even though your post is very hard to read, I guess I got the point.
I have the same issue and it is related to Cross Site Scripting / Cross Origin stuff (open the dev console in your browser and look for warnings/error messages).
I executed this command docker exec -u postgres metasfresh_docker_db_1 psql -d metasfresh -c "UPDATE AD_SysConfig SET Value='http://my_metasfreshinstance.com' WHERE Name='webui.frontend.url';" (it shall help; see https://forum.metasfresh.org/t/docker-install-rest-scripts-have-incorrect-cors-headers-cannot-login/1705).
But I still have the white page and a Cross Origin warning.
Unfortunately, I did not find any solution, yet.
There was a github issue https://github.com/metasfresh/metasfresh-docker/issues/52 but the solution was not really mentioned.

Marius_R · October 20, 2020, 10:48am

Seems like a Port/URL Problem.
If you access via SSL try in webapi url port 9092 and wait after docker-compose up -d it takes several mins to initialize complete!
Here is my working docker-compose for SSL

db:
  build: db
  restart: always
  volumes:
    - ./volumes/db/data:/var/lib/postgresql/data
    - ./volumes/db/log:/var/log/postgresql
    - /etc/localtime:/etc/localtime:ro
    - /etc/timezone:/etc/timezone:ro
  environment:
    - METASFRESH_USERNAME=metasfresh
    - METASFRESH_PASSWORD=metasfresh
    - METASFRESH_DBNAME=metasfresh
    - DB_SYSPASS=System
    - POSTGRES_PASSWORD=ip2LmNzXX8p8iXg9lZTWEJ9524kQDbXFudB7LR03T-xK9fLweX3TLMkA2AYcEiaS
app:
  build: app
  hostname: app
  links:
    - db:db
    - rabbitmq:rabbitmq
    - search:search
  expose:
    - "8282"
    - "61616"
    - "8788"
  restart: always
  volumes:
    - ./volumes/app/log:/opt/metasfresh/log:rw
    - ./volumes/app/heapdump:/opt/metasfresh/heapdump:rw
    - /etc/localtime:/etc/localtime:ro
    - /etc/timezone:/etc/timezone:ro
  environment:
    - METASFRESH_HOME=/opt/metasfresh
webapi:
  build: webapi
  links:
    - app:app
    - db:db
    - rabbitmq:rabbitmq
    - search:search
  expose:
    - "8789"
# to access the webui-api directly 
# (eg. for debugging or connecting your app to the metasfresh api) 
# uncomment following port:
  #ports:
   #- "8080:8080"
  restart: always
  volumes:
    - ./volumes/webapi/log:/opt/metasfresh-webui-api/log:rw
    - ./volumes/webapi/heapdump:/opt/metasfresh-webui-api/heapdump:rw
    - /etc/localtime:/etc/localtime:ro
    - /etc/timezone:/etc/timezone:ro
webui:
  build: webui
  links:
    - webapi:webapi
  ports:
    - "8080:80"
    - "8443:443"
  restart: always
  volumes:
    - /etc/localtime:/etc/localtime:ro
    - /etc/timezone:/etc/timezone:ro
  #uncomment and set to URL where metasfresh will be available from browsers
  environment:
    - WEBAPI_URL=https://YOUR_WEBSITE.de:8443
rabbitmq:
  build: rabbitmq
  expose:
    - "5672"
  restart: always
  volumes:
    - ./volumes/rabbitmq/log:/var/log/rabbitmq/log
    - /etc/localtime:/etc/localtime:ro
    - /etc/timezone:/etc/timezone:ro
  environment:
    RABBITMQ_DEFAULT_USER: "metasfresh"
    RABBITMQ_DEFAULT_PASS: "metasfresh"
    RABBITMQ_DEFAULT_VHOST: "/"
search:
  build: search
  ulimits:
    memlock:
      soft: -1
      hard: -1
    nofile:
      soft: 65536
      hard: 65536
  cap_add:
    - IPC_LOCK
# to access the search api directly
# (e.g. if you did docker-compose up search to have the deachboard with your locally running metasfresh services)
# uncomment following ports:
# ports:
#   - "9200:9200"
#   - "9300:9300"
  volumes:
    - ./volumes/search/data:/usr/share/elasticsearch/data
    - /etc/localtime:/etc/localtime:ro
    - /etc/timezone:/etc/timezone:ro
  environment:
    - "ES_JAVA_OPTS=-Xms128M -Xmx256m"
  restart: always

TKlerx · October 22, 2020, 1:20pm

Thanks Marius. This config also works for me. It should be the default for the git repo

Sven · October 29, 2020, 8:26pm

Additional solution
The https:// part in the WEBAPI_URL will be overriden, see

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"] ```

for solution

Sai_Kumar_Dasari · October 30, 2020, 1:44pm

Thank you very much Admin.

CSaeum · November 26, 2020, 10:32am

How quickly is this transferred to the master branch?

Because that seems to have been my problem when I wrote the problem with the white page in the forum