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

[4.x]: Upgrading from Craft 4.0.6 to 4.1.0 - 502 Bad Gateway #11514

Closed
magnessjo opened this issue Jun 28, 2022 · 7 comments
Closed

[4.x]: Upgrading from Craft 4.0.6 to 4.1.0 - 502 Bad Gateway #11514

magnessjo opened this issue Jun 28, 2022 · 7 comments

Comments

@magnessjo
Copy link
Contributor

What happened?

Description

server throwing a 502 after upgrade

Steps to reproduce

  1. Update all plugins and craft to the latest before 4.1.0
  2. Then run update for Craft 4.1.0

Expected behavior

Actual behavior

Craft CMS version

4.1.0

PHP version

8.1.6

Operating system and version

OS

Database type and version

Mac 13.0 beta v2

Image driver and version

GD 8.1.6

Installed plugins and versions

NEO 3.1.5

@magnessjo
Copy link
Contributor Author

Seems related to custom module. I removed the module and update worked so I am going to dig deeper into the code.

@brandonkelly
Copy link
Member

@magnessjo Do you mind sending your module code over to support@craftcms.com so we can dig into it on our end? There shouldn’t be any breaking changes in 4.1.

@magnessjo
Copy link
Contributor Author

@brandonkelly - it's not the module (technically a plugin in this repo). I have removed it, cleared cache, did a rain dance and the error persists.

The project experiencing the issue is still in early draft state (mostly only front end development). Other production sites with much more complexity (custom module, OAuth, etc) are able to be updated to 4.1 without issue.

Happy to provide any code/db/etc but don't want to lead you down a rabbit hole. I'll still crossing things off my list but confident that it's not local env or module.

@RyanRoberts
Copy link

Same problem here, no custom module but I do have various plugins installed.

@magnessjo
Copy link
Contributor Author

I was able to track down the problem (not the solution),

in app.php - There is some generic code in place (I didn't add it - or at least I don't think I did - maybe part of the base now?)

Anyway, if you remove my-module' => \modules\Module::class,, then the error will go away.

@brandonkelly
Copy link
Member

We were able to reproduce with someone’s database, and just released Craft 4.1.0.1 with a fix. Thanks everyone!

@RyanRoberts
Copy link

We were able to reproduce with someone’s database, and just released Craft 4.1.0.1 with a fix. Thanks everyone!

This was the problem I was having, updating fixed it indeed.

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

No branches or pull requests

3 participants