Changed several versions, but the mobile phone interface still cannot be displayed in the browser

[doyus]

trafficstars

Changed several versions, but the mobile phone interface still cannot be displayed in the browser

[RajeevSebastian]

are you deploying on a local machine? looks like it

[doyus]

No, deployed on a remote machine

[YuhooZhu]

if status is unhealthy

[zastress]

I have the same issue, docker container logs show the following on MacOS: 2021-04-07 03:57:51,813 CRIT Supervisor running as root (no user in config file) 2021-04-07 03:57:51,815 INFO supervisord started with pid 8 2021-04-07 03:57:52,820 INFO spawned: 'xvfb' with pid 11 2021-04-07 03:57:52,823 INFO spawned: 'port-forward' with pid 12 2021-04-07 03:57:52,825 INFO spawned: 'novnc' with pid 13 2021-04-07 03:57:52,827 INFO spawned: 'openbox' with pid 14 2021-04-07 03:57:52,829 INFO spawned: 'x11vnc' with pid 15 2021-04-07 03:57:52,831 INFO spawned: 'screen-copy' with pid 17 2021-04-07 03:57:52,832 INFO spawned: 'docker-appium' with pid 18 2021-04-07 03:57:52,834 INFO spawned: 'atd' with pid 19 2021-04-07 03:57:52,836 INFO spawned: 'auto-recording' with pid 21 2021-04-07 03:57:52,837 INFO spawned: 'adb-utils' with pid 23 2021-04-07 03:57:52,842 INFO exited: atd (exit status 0; not expected) 2021-04-07 03:57:52,849 INFO exited: screen-copy (exit status 0; not expected) 2021-04-07 03:57:53,874 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2021-04-07 03:57:53,874 INFO success: port-forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2021-04-07 03:57:53,874 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2021-04-07 03:57:53,874 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2021-04-07 03:57:53,875 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2021-04-07 03:57:53,876 INFO spawned: 'screen-copy' with pid 142 2021-04-07 03:57:53,877 INFO success: docker-appium entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2021-04-07 03:57:53,879 INFO spawned: 'atd' with pid 144 2021-04-07 03:57:53,880 INFO success: auto-recording entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2021-04-07 03:57:53,880 INFO success: adb-utils entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2021-04-07 03:57:53,894 INFO exited: screen-copy (exit status 0; not expected) 2021-04-07 03:57:53,894 INFO exited: atd (exit status 0; not expected) 2021-04-07 03:57:54,588 INFO exited: docker-appium (exit status 0; expected) 2021-04-07 03:57:55,902 INFO spawned: 'screen-copy' with pid 167 2021-04-07 03:57:55,905 INFO spawned: 'atd' with pid 168 2021-04-07 03:57:55,908 INFO exited: screen-copy (exit status 0; not expected) 2021-04-07 03:57:55,910 INFO exited: atd (exit status 0; not expected) 2021-04-07 03:57:58,856 INFO exited: auto-recording (exit status 0; expected) 2021-04-07 03:57:59,680 INFO spawned: 'screen-copy' with pid 172 2021-04-07 03:57:59,683 INFO spawned: 'atd' with pid 173 2021-04-07 03:57:59,687 INFO exited: screen-copy (exit status 0; not expected) 2021-04-07 03:57:59,688 INFO gave up: screen-copy entered FATAL state, too many start retries too quickly 2021-04-07 03:57:59,689 INFO exited: atd (exit status 0; not expected) 2021-04-07 03:58:00,693 INFO gave up: atd entered FATAL state, too many start retries too quickly

[User-Clb]

I'm also having the same issue