Getting a more descriptive error message from my instance

Support
1

Hi all, I’m having a bit of trouble with my discourse.

My site is showing a 502 Bad Gateway on the home page like so,

image
image587×174 5.09 KB

Is there a way to get a more descriptive error message?

Is there a way to start my instance without any plugins?

Is there a page that will show the logs so I might be able to see what plugin might be causing the issue?

Is there a way to access the site at all through the browser? As in, can the admin pages still work even if the main site does not?

Basically, what do I do to start to solve this?

–
BTW Reading through more posts here, I might have done something to cause this inadvertently.
IIRC I went to the upgrade page and updated the plugins and then attempted to upgrade the Discourse core install. It didn’t say not to or suggest that install order mattered.
I used the upgrade page, not a terminal or command line.
If this is backwards or can cause issues please let me know.

1 Like
2

This almost certainly means you are not serving pages because the build didn’t complete successfully

Yes, look at your build log first (printed to console) when you run the build command. There’s probably an error there.

Comment out each plugin clone command with a leading # in app.yml and rebuild.

(disabling in admin menu is not a complete disable often)

3

Hi Robert,
I’m not using the command line but I upgraded through the site upgrade page. I’ve added a comment into my post.

I also feel a slight duty to test the site upgrade page and report errors. Though at this point in time I’d rather get my site back up and running so I will use a command line.

How do I do the suggestion above? The upgrade was last week through the browser.

1 Like
4

ssh into the server (as you did when you first built the instance), navigate to /var/discourse and run ./launcher rebuild app

3 Likes
5

I didn’t ssh into the machine. It was built by an auto installer. But I’ll see if I can do that. Thanks.

1 Like
6

can you elaborate?

that’s almost certainly not supported.

1 Like
7

I had a prebuilt instance created and setup. It might have been a docker instance or image. I didn’t do any command line install. But I found a terminal with my hosting provider and I’m running that command now. I’ll report back.

8

Just a suggestion. If it’s possible, can I run this command from the browser admin in the future. I don’t know if the update page does this already or not but if this is the fix all, it might be helpful to have it on the admin page.

Also, the log notes said it can take up to an hour to run. If I closed the browser window when I was doing an update through that would that cause an issue? It seemed unresponsive (no log messages for a while IIRC).

1 Like
9

Rebuilding worked. Took about one hour. Site is back.

My host had an online terminal feature that I was able to use to rebuild.

2 Likes
10

Would still like to volunteer these ideas for those who use the browser to upgrade. Or even a note in the upgrade page, maybe a link to a help page that says, “If anything goes wrong with this upgrade start here.”

1 Like
11

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