cancel
Showing results for 
Search instead for 
Did you mean: 

502 error on admin after theme change

502 error on admin after theme change

I just installed a new theme on my development server, seemed to go fine, front end looks OK, but when I try to log in to the admin. I'm getting a 502 Bad Gateway error (I use NGINX).

 

Any idea what might have happened here?

 

I took a peek at debug.log and see some things--not sure if this is relevant or not:

 

[2019-07-23 14:17:06] main.INFO: Broken reference: the 'global_notices' element cannot be added as child to 'global.notices', because the latter doesn't exist [] []
[2019-07-23 14:17:06] main.INFO: Broken reference: the 'logo' element cannot be added as child to 'header', because the latter doesn't exist [] []                                                                                           [2019-07-23 14:17:06] main.INFO: Broken reference: the 'global.search' element cannot be added as child to 'header', because the latter doesn't exist [] []                                                                                  [2019-07-23 14:17:06] main.INFO: Broken reference: the 'user' element cannot be added as child to 'header', because the latter doesn't exist [] []
[2019-07-23 14:17:06] main.INFO: Broken reference: the 'menu' element cannot be added as child to 'page.menu', because the latter doesn't exist [] []
[2019-07-23 14:17:06] main.INFO: Broken reference: the 'breadcrumbs' element cannot be added as child to 'page.breadcrumbs', because the latter doesn't exist [] []
[2019-07-23 14:17:06] main.INFO: Broken reference: the 'formkey' element cannot be added as child to 'page.formkey', because the latter doesn't exist [] []
[2019-07-23 14:17:06] main.INFO: Broken reference: the 'page.title' element cannot be added as child to 'main.top', because the latter doesn't exist [] []
[2019-07-23 14:17:06] main.INFO: Broken reference: the 'messages' element cannot be added as child to 'page.messages', because the latter doesn't exist [] []
[2019-07-23 14:17:06] main.INFO: Broken reference: the 'page.actions.toolbar' element cannot be added as child to 'page.main.actions', because the latter doesn't exist [] []
[2019-07-23 14:17:06] main.INFO: Broken reference: the 'legal' element cannot be added as child to 'footer', because the latter doesn't exist [] []
[2019-07-23 14:17:06] main.INFO: Broken reference: the 'notification_area' element cannot be added as child to 'notifications', because the latter doesn't exist [] []
[2019-07-23 14:17:06] main.INFO: Broken reference: the 'unread_system_messages' element cannot be added as child to 'notifications', because the latter doesn't exist [] []
[2019-07-23 14:17:06] main.INFO: Broken reference: the 'notification_window' element cannot be added as child to 'notifications', because the latter doesn't exist [] []
[2019-07-23 14:17:06] main.INFO: Broken reference: the 'notification.messages' element cannot be added as child to 'header', because the latter doesn't exist [] []
[2019-07-23 14:17:06] main.INFO: Broken reference: the 'header.inner.left' element cannot be added as child to 'header', because the latter doesn't exist [] []
[2019-07-23 14:17:06] main.INFO: Broken reference: the 'header.inner.right' element cannot be added as child to 'header', because the latter doesn't exist [] []
[2019-07-23 14:17:06] main.INFO: Broken reference: the 'logo' tries to reorder itself towards '', but their parents are different: 'header' and '' respectively. [] []
[2019-07-23 14:17:06] main.INFO: Broken reference: the 'global.search' tries to reorder itself towards 'logo', but their parents are different: 'header' and '' respectively. [] []
[2019-07-23 14:17:06] main.INFO: Broken reference: the 'user' tries to reorder itself towards '', but their parents are different: 'header' and '' respectively. [] []
[2019-07-23 14:17:06] main.INFO: Broken reference: the 'page.actions.toolbar' tries to reorder itself towards '', but their parents are different: 'page.main.actions' and '' respectively. [] []
[2019-07-23 14:17:06] main.INFO: Broken reference: the 'notification.messages' tries to reorder itself towards 'user', but their parents are different: 'header' and '' respectively. [] []
4 REPLIES 4

Re: 502 error on admin after theme change

OK, I restarted PHP and now I'm in the backend. But what exactly could be going on here? My PHP memory limit was already increased according to the Magento specifications....

 

Something in this theme is causing PHP to work extra hard maybe?

Re: 502 error on admin after theme change

@ed_geisIs it continuously happening or was one time? One could be due to some of the PHP process go stuck in something. However, if this is happening frequently then you need to check:

 

  • If cache is enabled on your server?
  • You site is in Production mode instead of Default / Developer mode.
  • You did deploy static content?
  • If the issue still persist remove the theme to verify that new theme is causing the issue.

 

Problem solved? Please give 'Kudos' and accept 'Answer as Solution'.

- Tarandeep
Problem solved?Please give 'Kudos' and accept 'Answer as Solution'.

Re: 502 error on admin after theme change

Thanks, I will check those things you mentioned and report back.

Re: 502 error on admin after theme change

Below commands resolved issue for me :

find pub/static/ -type f -exec chmod 644 {} \; && find pub/static/ -type d -exec chmod 755 {} \;

and then just flush cache.