[Solved] 500 Internal Server Error on atenahub.app.br (Morty server)

[talesaz]

Hello HelioHost Support Team,

I am hosting my Flask application under the domain atenahub.app.br on the Morty server.

Since the server maintenance that occurred yesterday, I have been experiencing frequent "500 Internal Server Error" responses. I checked my access logs and noticed several automated malicious bot requests (directory fuzzing/scanning for .env files).

I am not entirely sure if these 500 errors are simply my application breaking due to these bot attack attempts, or if it is a side effect of the recent server maintenance/movement. Could you please verify the server status and help me investigate the root cause?

Additionally, to make my backend more robust and mitigate these brute-force/scanning attempts, I plan to implement a rate limiter. Could you please install the Flask-Limiter Python library on my server environment?

Thank you for your time and assistance!

[talesaz]

I have an additional request regarding my database on the Morty server.

I am trying to connect remotely to my MySQL database using HeidiSQL and my local Python environment for development purposes. However, I am consistently getting the following error:
Access denied for user 'talesaz_matrizhub00'@'2804:...' (using password: YES)

Here is what I have already checked and configured:

My credentials are 100% correct (I can access the database perfectly through phpMyAdmin in Plesk).

In Plesk > Databases > User Management, I have already set the Access Control to "Allow remote connections from any host".

Could you please verify if there is any server-side issue?

This database is related to matrizhub.heliohost.us

Thank you again for your time!

[MoneyBroz]

Your account was recently moved to the new morty server, did you update all of the references from morty.heliohost.org to morty2.heliohost.org?

[talesaz]

Hi MoneyBroz,

Thank you for the update. Changing the hostname to morty2.heliohost.org fixed my remote database access via HeidiSQL.

However, the production site atenahub.app.br is still returning a 500 Internal Server Error even after updating the internal database connection strings.

Since my account was recently moved to the new server, The Python + Flask environment and WSGI configurations were fully preserved during the migration?

The WSGI restart/reload mechanism is functioning correctly for my account on morty2?

Thanks!

[wolstech]

Quote

The Python + Flask environment and WSGI configurations were fully preserved during the migration?

No they are not. Python modules you requested be installed (and I think WSGI control if it was enabled) do not carry over. Did you request either of these?

If so, you'll need to request them again.

[talesaz]

30 minutes ago, wolstech said:

No they are not. Python modules you requested be installed (and I think WSGI control if it was enabled) do not carry over. Did you request either of these?

If so, you'll need to request them again.

Hi,

Thank you for clarifying! That explains the silent 500 errors perfectly. Yes, I do need the WSGI control enabled for atenahub.app.br (I'm aware of the extra costs), and I need my Python modules reinstalled on the new server.

Could you please enable WSGI and install the following Python libraries for my account?

• Flask
• Flask-SQLAlchemy
• Flask-Login
• Flask-Limiter
• mysql-connector-python
• firebase-admin
• requests
• Pillow
• pypdf
• qrcode
• mercadopago

Additionally, could you please share the pyinfo link for the new morty2 server? I used to check https://krydos3.heliohost.org/pyinfo/info3.12.py on the old server to verify my environment and installed modules, and it would be very helpful to have the new equivalent link.

I really appreciate your help in getting the application fully back online!

Best regards.

[KazVee]

This support request is being escalated to our root admins who can add the modules and WSGI control for you, and confirm if there's a morty2 pyinfo link set up.

[MoneyBroz]

Here is the pyinfo page for both 3.9 & 3.14

https://morty2-info.heliohost.org/pyinfo/

[Krydos]

This is why we emailed you on April 27th to let you know you were going to be moved. A lot of people actually read that email and then requested the Python modules they needed before they even moved, and realized they were going to have to change their remote database string, etc. We also posted the same news on this forum, Discord, Facebook, etc. If you had read that email and told us the modules you needed 2 weeks ago there wouldn't have been any 500 errors.

Modules installed.

[talesaz]

Hi Krydos and MoneyBroz,

First, thank you MoneyBroz for providing the pyinfo link earlier, I really appreciate it!

Krydos, you are absolutely right, and I apologize for missing that specific instruction in the April 27th email. I saw the news about the hardware upgrade but completely overlooked the part about having to re-request the modules. My mistake, and thank you for installing them so quickly!

However, my production site (atenahub.app.br) is still returning a 500 Internal Server Error. Could you please help me to know what Python/WSGI exception is being triggered?

Thank you again for your patience and support!

Best regards.

[Krydos]

Which domain?

[talesaz]

4 minutes ago, Krydos said:

Which domain?

Hi Krydos,

The domain is atenahub.app.br.

While you are checking it, could you please confirm if the WSGI restart/reload control is enabled for this specific domain? Just to reiterate, I am fully aware of and accept the extra costs associated with having this option enabled on my account.

Thank you again for looking into this so quickly!

Best regards.

[Krydos]

TabError: inconsistent use of tabs and spaces in indentation File "/home/talesaz.heliohost.us/atenahub.app.br/config.py", line 7

[talesaz]

Hi Krydos,

Ah, I love Python, but those strict tabs vs. spaces indentation errors are the absolute bane of my existence! 😅

Thank you for catching that in the logs. I just went in, fixed the indentation in config.py, and saved the file. I also tried to trigger a WSGI restart on my end.

However, the site is still returning a 500 error for me. Could you please check if the WSGI restart actually went through, or if the log is showing a new error now that the TabError is out of the way?

Thanks again for the help!