# 502 Bad Gateway after updating to Version 9.0.5+6706

**URL:** <https://community.localwp.com/t/502-bad-gateway-after-updating-to-version-9-0-5-6706/43717>\
**Category:** Support\
**Tags:** mac\
**Created:** [July 12, 2024, 9:44am UTC](https://community.localwp.com/t/502-bad-gateway-after-updating-to-version-9-0-5-6706/43717 "2024-07-12T09:44:45Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![revrot](https://avatars.discourse-cdn.com/v4/letter/r/e480ec/32.png) [@revrot](https://community.localwp.com/u/revrot)\
**Post date:** [July 12, 2024, 9:44am UTC](https://community.localwp.com/t/502-bad-gateway-after-updating-to-version-9-0-5-6706/43717/1 "2024-07-12T09:44:45Z")

</div>

### What issue or error are you experiencing?

All my sites are showing Bad Gateway after updating to Version 9.0.5+6706 on mac

* * *

### What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc

Attempt to access any existing website - no joy  
Add new local site - No joy

* * *

### System Details

- **Local Version:** 9.0.5+6706

- **Operating System (OS) and OS version:**

- iMac Retina 5K, 27-inch, 2017

- Mac OS 13.6.7 (22G720)

* * *

### Local Logs

Attach your Local Logs here ([Help Doc - Retrieving Local’s Log](https://localwp.com/help-docs/troubleshooting/retrieving-locals-log-file/))  
[local-lightning-verbose.log](https://community.localwp.com/uploads/short-url/tvWzlIP5L6faeqcL4A7rhn4R9x1.log) (594.2 KB)

* * *

_ **Security Reminder** _  
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.

 ![Screenshot 2024-07-12 at 10.50.30](https://us1.discourse-cdn.com/flex019/uploads/lwpforums/original/3X/b/5/b5182de6b57e7458ae698f77dce5d03f3771b6c8.png)  
 ![Screenshot 2024-07-12 at 10.51.36](https://us1.discourse-cdn.com/flex019/uploads/lwpforums/original/3X/0/b/0b4f907364cccd0182ee497e0147044cfe493b3b.jpeg)  
 ![Screenshot 2024-07-12 at 10.52.28](https://us1.discourse-cdn.com/flex019/uploads/lwpforums/original/3X/8/3/835a490a8adf83a5486812fc1f593ee9e533efcd.png)

---

<div class="post-metadata">

**Author:** ![Nick-B](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nick-b/32/16140_2.png) [@Nick-B](https://community.localwp.com/u/Nick-B)\
**Post date:** [July 12, 2024, 1:06pm UTC](https://community.localwp.com/t/502-bad-gateway-after-updating-to-version-9-0-5-6706/43717/2 "2024-07-12T13:06:45Z")

</div>

Hi @revrot did you try downgrading back to see if that fixes the issue?

> **[Downgrade Local Version](https://localwp.com/help-docs/troubleshooting/downgrade-local-version/)**
>
> Downgrading Local may be used to troubleshoot issues presented with a newer version or other various reasons. We recommend running Local on the latest version available when possible.

---

<div class="post-metadata">

**Author:** ![revrot](https://avatars.discourse-cdn.com/v4/letter/r/e480ec/32.png) [@revrot](https://community.localwp.com/u/revrot)\
**Post date:** [July 12, 2024, 4:38pm UTC](https://community.localwp.com/t/502-bad-gateway-after-updating-to-version-9-0-5-6706/43717/3 "2024-07-12T16:38:56Z")

</div>

> [@Nick-B](#):
>
> wngrading back to see if that fixes the issue?

Thank you Nick-B, I dont remember the version I was using before the update so I just downloaded Version 8.2.0+6554 and that did the trick, Im back up and running for now. thank you.

---

<div class="post-metadata">

**Author:** ![Nick-B](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nick-b/32/16140_2.png) [@Nick-B](https://community.localwp.com/u/Nick-B)\
**Post date:** [July 13, 2024, 1:42pm UTC](https://community.localwp.com/t/502-bad-gateway-after-updating-to-version-9-0-5-6706/43717/4 "2024-07-13T13:42:12Z")

</div>

Glad to hear things are working like normal again @revrot! We aren’t able to replicate this issue on 9.0.5 or have any other widespread reports at this time, but you’re welcome to stay on that version if you like. We’ll be here if you need to update later and want to troubleshoot further or wait until the next release.

---

<div class="post-metadata">

**Author:** ![bamstian](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/bamstian/32/22227_2.png) [@bamstian](https://community.localwp.com/u/bamstian)\
**Post date:** [July 16, 2024, 10:54am UTC](https://community.localwp.com/t/502-bad-gateway-after-updating-to-version-9-0-5-6706/43717/5 "2024-07-16T10:54:54Z")

</div>

Same here for me. Since this happened multiple times over the last years I will no longer use LocalWP or any WP Engine Product. I can not access my Blueprints anymore, which would not happend if I had used a professional tool like XAMMP or Docker.

I did try to downgrade and did everything you can find in this forum regarding 502 Error.  
Whenever I updated an Installation or Blueprint the 502 Error appears regardless what I did to fix this ISSUE!

It has been the same for the last couple of years. Im done.

---

<div class="post-metadata">

**Author:** ![Nick-B](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nick-b/32/16140_2.png) [@Nick-B](https://community.localwp.com/u/Nick-B)\
**Post date:** [July 16, 2024, 1:26pm UTC](https://community.localwp.com/t/502-bad-gateway-after-updating-to-version-9-0-5-6706/43717/6 "2024-07-16T13:26:44Z")

</div>

Thank you for the feedback here @bamstian

I don’t see any history under your user as far as past troubleshooting, but if you ever come back to Local and need any further assistance, keep us posted here, and we’ll be glad to take a look. We understand doing what is best for your workflows and needs.

---

<div class="post-metadata">

**Author:** ![bamstian](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/bamstian/32/22227_2.png) [@bamstian](https://community.localwp.com/u/bamstian)\
**Post date:** [July 16, 2024, 2:29pm UTC](https://community.localwp.com/t/502-bad-gateway-after-updating-to-version-9-0-5-6706/43717/7 "2024-07-16T14:29:42Z")

</div>

Sure, because I never posted. I will not come back. You do not understand what is best for workflows when you product is killing my blueprints. Obviously.

Have a good one

---

<div class="post-metadata">

**Author:** ![ben.turner](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/ben.turner/32/5366_2.png) [@ben.turner](https://community.localwp.com/u/ben.turner)\
**Post date:** [July 16, 2024, 4:34pm UTC](https://community.localwp.com/t/502-bad-gateway-after-updating-to-version-9-0-5-6706/43717/8 "2024-07-16T16:34:46Z")

</div>

@revrot – Thanks for that screenshot of the browser window along with the console errors you were seeing. That helps me better visualize a potential issue that might be happening. It’s almost like an ipv6 (`::1`) is being incorrectly added as a port to those urls:

 ![Zight 2024-07-16 at 9.31.14 AM.jpg](https://us1.discourse-cdn.com/flex019/uploads/lwpforums/original/3X/6/3/630e4d0cdfe13f097bc129c732b441d643709f80.jpeg)

I don’t have a fix, but mostly just observing and wanted to say thank you!

---

<div class="post-metadata">

**Author:** ![Pegasus](https://avatars.discourse-cdn.com/v4/letter/p/278dde/32.png) [@Pegasus](https://community.localwp.com/u/Pegasus)\
**Post date:** [July 20, 2024, 2:47pm UTC](https://community.localwp.com/t/502-bad-gateway-after-updating-to-version-9-0-5-6706/43717/9 "2024-07-20T14:47:01Z")

</div>

Try setting PHP 8.20 or 7.4.30 but stay cleaver of PHP 8.1.29 with this I wasn’t able to install any sites

Hope it helps

---

<div class="post-metadata">

**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/system/32/1_2.png) [@system](https://community.localwp.com/u/system)\
**Post date:** [October 18, 2024, 2:47pm UTC](https://community.localwp.com/t/502-bad-gateway-after-updating-to-version-9-0-5-6706/43717/10 "2024-10-18T14:47:44Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
