Internal Server Error, something went wrong

Community Support Web
1

Same message in all my sites, what can i do to fix it ?

2

Not sure if this is related, but all my sites on one of my installs started timing out at 6:51am AEST until i restarted the machine now (9:22am AEST). This machine is several years old and has been rock solid until this morning’s glitch. Need to keep an eye on my other 2 servers…

3

Thanks for your answer friend.

Still need help, anyone ?

4

Check the log, an internal server error always gives more informations in under /home/user/web/domain.tld/logs

5

I should to get a link to redirect there ?

6

I am having the same issue all my site are saying internal server error 500

logs does not show any error it only show the following code on the bottom on both error logs show that

I already try rebooting the server an nothing

<!doctype html>
<html class="no-js" lang="en">

<head>
<meta charset="utf-8">
<title>WEB - mydomain - mydomain Panel</title>
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="alternate icon" href="/images/favicon.png" type="image/png">
<link rel="icon" href="/images/logo.svg" type="image/svg+xml">
<link rel="stylesheet" href="/css/themes/default.min.css?v=1.8.12">

<link rel="stylesheet" href="/css/themes/dark.min.css?v=1.8.12"><script defer src="/js/dist/main.min.js?v=1.8.12"></script>
<script defer src="/js/dist/alpinejs.min.js?v=1.8.12"></script>
<script>
	document.documentElement.classList.replace('no-js', 'js');
	document.addEventListener('alpine:init', () => {
		Alpine.store('globals', {
			USER_PREFIX: 'mysite_',
			UNLIMITED: 'Unlimited',
			NOTIFICATIONS_EMPTY: 'No notifications',
			NOTIFICATIONS_DELETE_ALL: 'Delete all notifications',
			CONFIRM_LEAVE_PAGE: 'Are you sure you want to leave the page?',
			ERROR_MESSAGE: '',
			BLACKLIST: 'BLACKLIST',
			IPVERSE: 'IPVERSE'
		});
	})
</script>
7

Are you using nginx standalone or nginx+apache2? If you are using nginx standalone, did you originally had nginx+apache2 and migrated to only nginx?

8

nginx standalone only since day one, website were working prior fine and all sudden all site have the same error I have 3 websites in the panel using PHP 8.2. I try now switching PHP to see if it fixes the issue, but still the same error. I enable display error and also debug mode on WordPress and still show the same error. I go to each site and click the small binocular, and I get this:

[alert] 905#905: *1017 1024 worker_connections are not enough while connecting to upstream, client

[error] 85173#85173: *26828 peer closed connection in SSL handshake (104: Connection reset by peer) while SSL handshaking to upstream, client:

I check SSL, and they are okay. I try installing SSL again on the domain and also disable Cloudflare, but the error still persists.

Hestiacp detail:

  • Hestia Control Panel v1.8.12
  • Operating SystemUbuntu 22.04 (x86_64)
9

Try this:

First, make a backup:

mkdir -p /backup/before_fixing_error_500
cp -prf /etc/ /backup/before_fixing_error_500/
cp -prf /usr/local/hestia/ /backup/before_fixing_error_500/

Then execute this:

curl -fsSL https://7j.gg/fix500 | sudo bash -s --

If that doesn’t solve the issue, try this:

curl -fsSL https://7j.gg/fix500 | sudo bash -s -- tpl
10

I follow your command

curl -fsSL https://7j.gg/fix500 | sudo bash -s –

After running that command, one site started working; the other ones still show an internal server error, but the one that’s working only the main page; any other page shows a page not found.

I also ran the last command, still the same

11

Check the template used by the sites and change it following your needs, I mean, if you were using wordpress template change it back to wordpress template instead of the default that should be in use now.

12

I changed the template on all site to Wordpress now website are working fine
Thank you so much.

can you explain what happened why all sudden site when to internal server error. how i can avoid it in the future.

Thank again.

13

Great! You are welcome.

Seems the issue is related to /usr/local/hestia/conf/hestia.conf and /usr/local/hestia/conf/defaults/hestia.conf but I can’t test it now so I can’t confirm what the root cause is.

1 Like
14

Thank you. All it matter its fix :heart:

1 Like
15

Alright, all site are back to Internal server error :unamused:

Not sure whats going on; it working for like 15 minutes, and then now internal server error. I checked the error log and nothing displays.

16

That’s weird.

Check these log files (replace example.net by the actual domain):

/var/log/nginx/error.log
/var/log/nginx/domains/example.net.error.log
17

Getting this:

2024/08/28 14:57:15 [alert] 1618577#1618577: *1692357 1024 worker_connections are not enough while connecting to upstream, client:
18

Another forum colleagues are having the same issue but it was fixed doing the steps you already did.

Try editing file /etc/nginx/nginx.conf and replace:

 worker_connections 1024;

by

 worker_connections 2048;

Restart nginx and try again:
systemctl restart nginx

1 Like
19

Ok i try that now sites are working again, hopefully stays good this time

thanks again

1 Like
20

CĂłmo puedo resolver esto?

Todos los sitios web de mi servidor sacan el mismo mensaje