It's showing me this error, my username is tuhinsarkar. Please help me with this. The domain or account related to this is globalyouthsciencejournal.app

[tuhinsarkar]

Error: filemng: Failed to change directory to /home/globalyouthsciencejournal.helioho.st/git/website: No such file or directory System error 2: No such file or directory

 

Server Error

500 Plesk\Exception\Database

DB query failed: "SET sql_mode = ''" Error code: 2002 Error: SQLSTATE[HY000] [2002] No such file or directory

Type	Plesk\Exception\Database
Message	DB query failed: "SET sql_mode = ''" Error code: 2002 Error: SQLSTATE[HY000] [2002] No such file or directory
File	Mysql.php
Line	68

You may be able to resolve the issue automatically using Repair Kit.
If you are the server administrator, try resolving the issue using our troubleshooting tool, Repair Kit.

Open Repair Kit

You will be asked to enter the Plesk administrator password.

Need help resolving the issue? Visit Plesk Help Center.

That's what you can do

Reload PageBack to Previous PageHome PageSearch for related Knowledge Base articles

Report a problemDocumentationKnowledge baseForumYouTubeFacebook

Edited 9 hours ago by tuhinsarkar

[KazVee]

The error mentions "Failed to change directory to /home/globalyouthsciencejournal.helioho.st/git/website" however the site you're seeing the error on is actually "globalyouthsciencejournal.app", is this correct? You're trying to connect to a directory inside the helioho.st site from the .app site?

When I check globalyouthsciencejournal.app, I see a different error now: 

Database Connection Error: SQLSTATE[HY000] [1105] Connections using insecure transport are prohibited. See https://docs.pingcap.com/tidbcloud/secure-connections-to-serverless-tier-clusters

Edited to add: We have some info in the Wiki for the "DB query failed: "SET sql_mode = ''" Error code: 2002 Error: SQLSTATE[HY000] [2002] No such file or directory" message here: https://wiki.helionet.org/500_Database_Error 

[tuhinsarkar]

The thing is I've uploaded the right code and everything in globalyouthsciencejournal.helioho.st that one everything works. The correct DB, no problem at all. The problem starts when I try to use my domain in the site. The domain is globalyouthsciencejournal.app. In my dashboard, that's the one that's showing all the problems. The globalyouthsciencejournal.helioho.st is fine. 

[wolstech]

Is your goal to make https://globalyouthsciencejournal.app/ show the same content as globalyouthsciencejournal.helioho.st? Or is the content supposed to be different on the .app site?

If they're supposed to be identical, an alias is probably an easier route than duplicating the site and figuring out why the .app copy is broken.

[tuhinsarkar]

6 hours ago, wolstech said:

Is your goal to make https://globalyouthsciencejournal.app/ show the same content as globalyouthsciencejournal.helioho.st? Or is the content supposed to be different on the .app site?

If they're supposed to be identical, an alias is probably an easier route than duplicating the site and figuring out why the .app copy is broken.

 

I am happy with either setups. I can try to do both. As long as globalyouthsciencejournal.app works. Right now it's not working, that's my concern. 

[tuhinsarkar]

6 hours ago, wolstech said:

Is your goal to make https://globalyouthsciencejournal.app/ show the same content as globalyouthsciencejournal.helioho.st? Or is the content supposed to be different on the .app site?

If they're supposed to be identical, an alias is probably an easier route than duplicating the site and figuring out why the .app copy is broken.

Please make the site work as soon as possible. For now you can make it copy globalyouthsciencejournal.helioho.st and show the same content. 

If possible you can setup an alias. But I need it to work as soon as possible, sorry. 

[KazVee]

All staff are unpaid volunteers. It is also a long holiday weekend in the USA, where many of the unpaid volunteer staff are based. 

Most for-profit hosting companies have a staff of full time employees who sit around providing support and working 40 hours a week. It's very rare for any of our volunteers to work more than an hour or so each day. None of our volunteers are required to log a certain number of hours and may come and go as they please.

If we aren't having fun volunteering, providing support, chatting with the community, and developing new features then we take a break and do things that are more fun for us. This is why we don't have SLAs or ETAs for new features or repairs, and this is why things move a little slower than a for-profit company that you might be used to dealing with.

Help is generally provided within 24 hours, and we encourage users to bump their requests if it's been more than 24 hours with no response, in case we missed it somehow.

Our best efforts to respond within 24 hours can be impacted by several factors, including but not limited to:

• Time zone differences (most staff are based in North America)
• Work
• School
• Family
• Other real-life commitments

For more information, please review the ETA page in our Wiki: https://wiki.helionet.org/ETA 

If you are unable to access the Wiki, please provide the IP address displayed on the error page. Thanks!

[tuhinsarkar]

13 minutes ago, KazVee said:

All staff are unpaid volunteers. It is also a long holiday weekend in the USA, where many of the unpaid volunteer staff are based. 

Most for-profit hosting companies have a staff of full time employees who sit around providing support and working 40 hours a week. It's very rare for any of our volunteers to work more than an hour or so each day. None of our volunteers are required to log a certain number of hours and may come and go as they please.

If we aren't having fun volunteering, providing support, chatting with the community, and developing new features then we take a break and do things that are more fun for us. This is why we don't have SLAs or ETAs for new features or repairs, and this is why things move a little slower than a for-profit company that you might be used to dealing with.

Help is generally provided within 24 hours, and we encourage users to bump their requests if it's been more than 24 hours with no response, in case we missed it somehow.

Our best efforts to respond within 24 hours can be impacted by several factors, including but not limited to:

• Time zone differences (most staff are based in North America)
• Work
• School
• Family
• Other real-life commitments

For more information, please review the ETA page in our Wiki: https://wiki.helionet.org/ETA 

If you are unable to access the Wiki, please provide the IP address displayed on the error page. Thanks!

I understand your concern. I run a non-profit as well, so I completely get it.

 

When I said "as soon as possible," I truly meant whenever possible. Whenever you and the other volunteers have the time, I'd really appreciate it if you could get to it when you can.

 

There's absolutely no pressure, and I'm sorry if my wording came across that way. I really appreciate the time and effort you're all volunteering. Thank you.