All Activity

Issue #1 is worth more like one of those Sushi Roll things. You ever have one of those? It's like a burrito from Taco Hell. only, it costs about as much as if you ordered burritos for the team. office. cubical. so, #1 get's that. that other things just like. i say not even a snickers. i guess. i been waitin. HAHAHA! that's right. laugh it up, pally (talks to self) EDIT - verified - > composer dump-autoload executed successfully (at least didn't report error)

I have the "demo app" here: Edit: sorry folks. i know i messed with this when i first came on in Feb. I can't remember details or where notes may be (at this time). I recall getting this error ("the slightly uncommon perhaps VPS-usually type error i'd mentioned) ``` Warning: opendir(): open_basedir restriction in effect. ``` I think that's more the issue, vs the template thing. but i don't think i have the template thing correct either. thank you!

If you enable Node through Plesk and let Passenger handle it, the server should start it when needed and kill it when it has no traffic. This only works for apps that receive HTTP traffic though. Passenger launches the app when the traffic comes in, and kills it after a period of inactivity. If you start it manually with npm run start or similar, you have to contact support and ask for your processes to be killed. There is no way to kill a manually started node process, and as a result, our typical recommendation is to never start a node process manually. We do offer VPS service with full SSH root access if you want total control over the app: https://heliohost.org/vps/ Those start at $4/month and come as an empty linux VM. You'll need to install node and anything else you need.

I'll guess you didn't read the instructions for that test completely... By "real email", we mean an actual message you've sent someone, with a body and subject. You sent an empty email... -2.344 EMPTY_MESSAGE Message appears to have no textual parts and no Subject: text -1.767 MISSING_SUBJECT Missing Subject: header Add a subject to your message! -1.985 PYZOR_CHECK Similar message reported on Pyzor (https://www.pyzor.org) https://pyzor.readthedocs.io/en/latest/ Please test a real content, test Newsletters will always be flagged by Pyzor Adjust your message or request whitelisting (https://www.pyzor.org)

wish to serve .phtml Hestia forum topic relevant(1) as necessary for an application i want to run. it's super basic why it's .phtml -- just for server-side logic. kind of like laravel.blade.php or whatever, just the actual extension is diff. it's not super uncommon, but i don't have any php.ini directives set to accomodate. (1) - followed these steps (i think. rem i have brain damage, so this is a bit more complicated than i'm used to and doing steps i'm unfamiliar with [ vs. the so-called motor-memory stuff i can just do without reason! haha ]) but failed. Perhaps i didn't run that command line admin script. i could REALLY use a hodling hand. my hand held. what the schwaw ever can someoine please help me with this directly? Please have a look at this as it's been a while i've been messing with it to no avail. I may not have addressed this with you guys yet however as it seems an issue i should be able to handle. however, it's crtically become time i'm able to actually be productive with it. i have only ever experienced this problem (so far) with the VPS config when I get the following: Warning: opendir(): open_basedir restriction in effect. SERVER CONF ISSUE (allow php to do the readdri thing i suppose. i realize but it's i promise its not doingn any nefarious business!) ideally 2 col table here! haha. the Warning: opendir() -- that's a PHP error output (like we've seen and know so well. Like Old Gregg!) HORZONTAL LINE [that gddm smokin that vaporizor then what do i accomplish - whatswrongwithyou! ] this being the right col/ separate iissue, which is more like Curly Jefferson. maybe ya'll are in process of working on it. ISSUE TWO - sort of server conf issue. much less expensive however. this one is more like the cost of a fireball. or i dont think it's even worth a snickers. thank you! P.S. When I first "signed-on" so to speak (became a member), I was offered a second subdomain (i think that was the offer? - where my takeaway was e.g vps112.heliohost.us or guitarguy.heliohost.us or whatever). it would be super awesome if i could get that. as i'm experimenting w/ Python stuff and i see it's preferable to have in the root of web public_html domain part. blah blah. You're awesome! 🤟

Secondly, I don't know why I'm getting 500 error.

https://www.mail-tester.com/test-eymxn1ls1

Hello, Could you please guide me on how to run a FastAPI server on shared hosting? Previously, I used uvicorn to run it locally, but since I don’t have root access on this shared hosting environment, I’m unsure how to proceed. I’ve already uploaded a folder named "app" that contains my FastAPI code. Thank you!

Thanks

We looked into this further and found that the command `npm run start` was run: | sum(mem) | sum(cpu) | process | +----------+----------+-------------------------------------------------+ | 24064 | 0.00 | /usr/bin/hostnamectl --transient | | 1602836 | 2.30 | Passenger NodeApp: /home/gantelya111.helioho.st | | 36087868 | 0.90 | npm run start:bootstrap | | 45013376 | 1.60 | node --max-old-space-size=460 bootstrap-node.js | | 56514848 | 2.70 | npm run start | | 70923448 | 4.30 | node bootstrap-node.js | The `npm run start` command is not part of the Node guidance page I'd sent you after the 1st unsuspension, so it may be that you did not read the guide. The Node.js Wiki page offers steps to ensure that your Node apps run on Passenger, which is a service on Plesk that helps to reduce Node's memory usage. Running commands that never exit (like `npm run start`) use a LOT more memory. If you need to continue using this command, and so much memory, we'd recommend you upgrade your account to the Morty server. Please make sure to review the Moving Your Account page for more details on the process, and make sure to backup your account before any account move. Once you're ready to move your account, you can begin the automated process from the Dashboard page for account moves. In the meantime, your account has been unsuspended. If you decide to keep your account on the Tommy server, we would strongly recommend checking the Node guidance page linked above, and making sure your app uses Passenger. Please fix the issue quickly since without any code changes, another suspension is likely. Please also be aware of the Three-Strike Policy section of our Suspension Policy.

DKIM, SPF, and DMARC have been set up for the domain theopengamer.com. We recommend sending a real email (not just the word "test") to https://www.mail-tester.com/ to make sure that everything is set up correctly. If you get less than a 10/10 score please post a link to the full report so we can help you fix any other issues that there may be.

Installed. You can see the current list of modules and their versions on Johnny's Python 3.12 with this link https://krydos2.heliohost.org/pyinfo/info3.12.py

Please check your PMs for information regarding your Lily account.

Okay, that's something I can do for you. 🙂 Which domain did you want as the main domain, and which one did you want as the addon domain? The only difference is that the main domain will have its files inside the httpdocs folder and the addon domain will have its files inside a folder with the same name as the addon domain. No functional differences.

just ignore the alias one, make it so papale.my.id and plj.my.id is separate, not an alias of one of theme

In the Linux operating system, the Node.js process may not be shut down or killed normally. This is usually related to process management, port occupation and exception handling. When we run a node.js process on a vps with full commands and permissions, we can use the ps and kill commands to find and end them, but in an virtual environment where only allows npm using, we have no way to end it. Even if we use disable node.js to end it, the node.js will still continue to run in the background.

Node is one of the top reasons for users to get their accounts suspended. Please check out our Node.js guidance page for ways to keep the load low. If you have a support request, please make sure you create a new thread for yourself and let us know what the issue is. All staff are volunteers who help in their free time and it can be confusing for us to troubleshoot issues for 2 different users in the same thread. 🙂

I was also surprised that my Node.js project also ran for a short period of time, but the memory was about to reach the upper limit, which forced me to terminate my project early. There was obviously a problem with the memory and CPU usage.

or change the payment plan for a higher limit

first I'll wait a day to knock down the limit completely, then I've already updated the code to reduce the load and added debugs, so I'll check if it helped and if the load continues I'll just disable the site and move to another programming language to see if it helps. I apologize for causing so much troubles. The question is why my code continued to load the server with node.js disabled

This support request is being escalated to our root admins who can help with aliases. Some added context from the old thread: this user is asking for papale.my.id to be the main domain and plj.my.id to be the alias one.

yeah, i thinks that this threads is marked solved so i make a new one

Same as yesterday, your account was suspended for High Server Usage due to using 200.14 GB memory when the daily limit is 200 GB. One account causing heavy load on the server impacts performance for the hundreds of other accounts on the same server. Since this is the 2nd suspension in 2 days and I don't see any changes to the load being used since the last time your account was unsuspended, I'll escalate this thread to the root admins. In the meantime, please provide clear steps explaining what you will do to immediately reduce the load your account is causing, to help the root admins make a decision about an unsuspension. Many thanks.

when i checked last time everything was ok, and memory usage was low

im quite surprised and im looking for the reason why my site using so much memory while it node.js were disabled, when i checked how much memory used it was quite late to do something so can im please being unsuspended?