Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bad Upstream #92

Open
kirk-brown-ew opened this issue Sep 5, 2022 · 2 comments
Open

Bad Upstream #92

kirk-brown-ew opened this issue Sep 5, 2022 · 2 comments

Comments

@kirk-brown-ew
Copy link

kirk-brown-ew commented Sep 5, 2022

I'm using Ubuntu 22.04 inside Parallels on an M1 Mac Air and I get the following error in the vhost-proxy logs when stopping and starting a Docksal project: [error] 1316#1316: *215 no live upstreams while connecting to upstream, client: 10.211.55.2, server: drupal.docksal.site, request: "GET /core/install.php HTTP/1.1", upstream: "http://drupal-web/core/install.php", host: "drupal.docksal.site"

In the web browser, the error is 502 Bad Gateway openresty/1.19.9.1

Docksal version: v1.17.0
fin version: 1.110.1

Steps to reproduce:

  1. Get Docker and the latest Docksal installed inside the Ubuntu 22.04 VM (Parallels used).
  2. Use fin create project to create a Drupal project named drupal using the Composer option.
  3. When you go to drupal.docksal.site, you can see the install screen.
  4. If you run fin project stop, then run fin project start, you'll get the 502 Bad Gateway error. This can happen if you stop the project, do a fin system stop and reboot the VM.
  5. To get the error log run: fin docker logs docksal-vhost-proxy
  6. The web and cli logs do not show any errors.
@kirk-brown-ew
Copy link
Author

I just created the Drupal project and instead of running fin project stop, I rebooted the vm and ran fin project start and it worked okay.

This leads me to believe that there's an issue with fin project stop.

@kirk-brown-ew
Copy link
Author

After running fin project stop and fin project start, if I run fin system reset vhost-proxy, the site will operate normally.

I'm hoping my notes help identify the issue and a fix can be found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant