platform launched but no app available (0.7 related)

Question

platform launched but no app available (0.7 related)

Closed this issue 6 years ago · 19 comments

Hi,
the docker is started, install script completed and 51 dockers apps started.
However when trying to connect to the URL:

for formio, http://api.formio.lab.ds/ error 503
for http://admin.lab.ds/ and http://portal.lab.ds/, the 3 color lines are looping and message "error while requesting anonymous token" but nothing
how to solve that?

BTW, is there a way to stop / start all docker created without going the install process ?

Answer 1 · 2018-07-21T18:54:15.000Z

with tag 0.7.0 , formio is now working compared to master release ... but lab.ds portal and admin are not with the same error.
I only updated the app parameter in lab/inventory.yml file.

Answer 2 · 2018-07-21T19:23:53.000Z

The default Portal and admin UI are broken in 0.7 due to rapid releases of tenants support and updated security due to tenants.

If you deploy 0.6 you should be okay

Answer 3 · 2018-07-21T19:31:43.000Z

Also make sure to check the instructions page for 0.6 as the steps may have changed

Answer 4 · 2018-07-21T21:29:55.000Z

For your formio issue, this was caused by the 0.7 update having a new microservice added to front the formio service. See: #35

Move to tag 0.6 if you want to use the UI at this time.

Answer 5 · 2018-07-21T23:22:07.000Z

tried with 0.6 but still getting "error while requesting anonymous token" message.
I will try again by flushing all docker images just in case of remaining data from other version...

Answer 6 · 2018-07-22T00:02:27.000Z

no luck :(

Answer 7 · 2018-07-22T01:56:50.000Z

You are using the postman collection provided in the platform repo?

What are the steps are you following?

Answer 8 · 2018-07-23T13:01:27.000Z

The playbooks structure changed a bit between 0.6 and 0.7, but to restart containers without a full reinstall: ansible-playbook app/container/up.yml.

There's also down.yml and stop.yml.

You can also supply a tag: ansible-playbook app/container/up.yml --tags="authentication" to only affect certain containers.

Answer 9 · 2018-07-25T11:46:46.000Z

I got the same issue and I had followed Lab Environment setup, that is, I modified inventory.yml values to:
encryption.secret: 11111111111111111111111111111111
jwt.pass_phrase: 1111
directory: /c/Users/illus/DockerProjects/Platform/app

and ran the playbook.

I haven't used Postman for anything.

Answer 10 · 2018-07-31T23:04:06.000Z

@Illusive7Man this is likely due to using Lab and 0.7.

Use tag 0.6 and use the Dev deployment (but modify it to use local rather than remote deployment). Lab uses the latest development branch, which is not guaranteed to be stable.
See the warning at the top of this page: https://github.com/DigitalState/Platform/blob/develop/platform/documentation/environments/lab/index.md#lab-environment

Answer 11 · 2018-07-31T23:04:42.000Z

@gismomtl did you make progress using the 0.6 and Dev deployment strategy?

Answer 12 · 2018-07-31T23:18:07.000Z

Hi,
yes following your advice I was able to have services available.
I'd to: use 0.6 tag, dev configuration with local deployment.
As I'd previously installed 0.7, dev, and master.. the docker images were a complete messed up..
even docker image prune was not sufficient... I'd to do a docker system prune -a --volumes

a great thanks for your support

Answer 13 · 2018-07-31T23:20:48.000Z

@gismomtl great! Make sure to check out the Postman collection and the updated docs in the current develop branch for further information about the APIs!

Answer 14 · 2018-08-04T11:05:21.000Z

Hey @gismomtl & @StephenOTT

Could you help me configure mine to localhost because I keep getting error when establishing ssh connection.

fatal: [platform]: FAILED! => {"changed": true, "cmd": "ssh-copy-id -i /root/.ssh/dev/key root@127.0.0.1", "delta": "0:00:00.301490", "end": "2018-08-04 10:54:23.560483", "msg": "non-zero return code", "rc": 1, "start": "2018-08-04 10:54:23.258993", "stderr": "/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/dev/key.pub"\n/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed\nexpr: warning: '^ERROR: ': using '^' as the first character\nof a basic regular expression is not portable; it is ignored\n\n/usr/bin/ssh-copy-id: ERROR: ssh: connect to host 127.0.0.1 port 22: Connection refused", "stderr_lines": ["/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/dev/key.pub"", "/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed", "expr: warning: '^ERROR: ': using '^' as the first character", "of a basic regular expression is not portable; it is ignored", "", "/usr/bin/ssh-copy-id: ERROR: ssh: connect to host 127.0.0.1 port 22: Connection refused"], "stdout": "", "stdout_lines": []}

What I've done is changed in inventory.yml is ansible_host to 127.0.0.1
I'm not familiar with Ansible, I am not sure what I'm doing exactly.
Windows 10

Edit:
ansible_connection: local, got me the same 503

Answer 15 · 2018-08-06T14:01:11.000Z

@Illusive7Man. What version of Windows and what version of docker are you using. You are using Windows 10 pro ? Docker toolkit Does not work. You must have Docker for Windows, which only works with Windows pro / hyperV

Answer 16 · 2018-08-06T16:55:39.000Z

@StephenOTT It's Windows 10 Pro. Docker version 18.06.0-ce (Docker for Windows)

Answer 17 · 2018-08-06T17:32:04.000Z

And to confirm: you are using Docker for Windows? Or using Docker Toolkit?

Answer 18 · 2018-08-06T17:44:45.000Z

@StephenOTT Docker for Windows

Answer 19 · 2018-08-06T18:20:48.000Z

I will create an issue, by tomorrow, with logs, system specifications and ansible files.