Krydos

WSGI control access has been enabled on the domain revokeauth.com. To restart your Flask app and load new code changes in simply edit /home/revokeauth.com/httpdocs/api/flask.wsgi. Adding a blank line, removing a blank line, adding a space, or removing a space are examples of editing the file. As long as the last modified timestamp changes it will clear the server cache. Let us know if you run into any issues.

Are you aware that WSGI control access uses about 260 GB memory per day, and your Morty bill will probably be about $1.91 or more per month?

Installed. You can see the modules and their versions on Morty's Python 3.12 with this link https://krydos3.heliohost.org/pyinfo/info3.12.py

I don't see anything obvious to delete. Backups 0 MB Emails 21.04 MB Files 1816.65 MB Trash .01 MB Logs 9.13 MB PSQL 0 MB MySQL 285.84 MB Total 2132.67 MB You're 132 MB over your limit. 881M /home/hostmysiteplease.helioho.st/httpdocs 12K /home/hostmysiteplease.helioho.st/harlemtechnologies.com 259M /home/hostmysiteplease.helioho.st/conarim.com 221M /home/hostmysiteplease.helioho.st/dhamira.co.ke 87M /home/hostmysiteplease.helioho.st/waa.co.ke 8.0K /home/hostmysiteplease.helioho.st/nilijua.xyz 24K /home/hostmysiteplease.helioho.st/private 12K /home/hostmysiteplease.helioho.st/.composer 109M /home/hostmysiteplease.helioho.st/yourcompanysolutions.online 8.0K /home/hostmysiteplease.helioho.st/mwenendo.xyz 263M /home/hostmysiteplease.helioho.st/mvuke.cloud 4.0K /home/hostmysiteplease.helioho.st/node 0 /home/hostmysiteplease.helioho.st/wordpress-backups 0 /home/hostmysiteplease.helioho.st/.wp-cli If you let us know what to delete we can delete it for you to get you back under the limit. You can also regain access to your account instantly without help from an admin if you want to upgrade your storage at https://heliohost.org/dashboard/storage/

Glad your account is still working after the domain shenanigans.

Not sure what you're even asking for. root@control [~]# dig +short A @ns1.heliohost.org webmail.tenkyuu.dev 64.62.151.106 root@control [~]# dig +short A @ns2.heliohost.org webmail.tenkyuu.dev 64.62.151.106 root@control [~]# dig +short AAAA @ns1.heliohost.org webmail.tenkyuu.dev 2001:470:1:1ee::2009 root@control [~]# dig +short AAAA @ns2.heliohost.org webmail.tenkyuu.dev 2001:470:1:1ee::2009 root@control [~]# dig +short A @ns1.heliohost.org webmail.bochard.net 64.62.151.106 root@control [~]# dig +short A @ns2.heliohost.org webmail.bochard.net 64.62.151.106 root@control [~]# dig +short AAAA @ns1.heliohost.org webmail.bochard.net 2001:470:1:1ee::2009 root@control [~]# dig +short AAAA @ns2.heliohost.org webmail.bochard.net 2001:470:1:1ee::2009 The DNS looks fine to me. Did you enable webmail in the mail settings? We were discussing this in the admin channel and our policy is when people decide they want to swap their main domain and an addon domain, like you just did, we will be requiring them to reset their account and start over entirely because we've done like 15 of these addon domain to main domain swaps now and every single one of them have broken the account in some irreparable way and the result is they end up needing to do a reset anyways. Looks like you broke your account by doing this as well. We usually try to talk people out of it because it's so much work for something that ultimately doesn't matter at all which domain is main and which domain is the addon.

DKIM, SPF, and DMARC have been set up for the domain appuris.com. We recommend sending a real email (not just the word "test" or a blank email) 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.

Closing due to inactivity since there has been no response in this thread for over a week. If you're still having this issue or need help with something else please open a new ticket.

The hourly sending limit of the email address that tried to exceed the 10 per hour limit has been increased to 50 emails per hour. The default limit of 50 emails per day remains the same for now. If you try to send more than 50 emails per day email sending privileges will be removed. This is the default limit, and since you didn't really answer question 1 (or any of the questions really) I assume the default limit is fine, and it's only the hourly limit that you need raised.

A second IPv4 would cost $2 per month. It looks like you're paying $5 per month now so that would bring the total to $7 per month. We would lose money if we sold IPv4 for less than we pay for them. If you click the follow button in the top right corner you will get email notifications when there are replies to this forum thread. You can also email support@heliohost.org if you want our replies to go to your email.

There's not much I can look at since you already deleted them. I guess if it happens again let us know without deleting them first.

I feel like I've already explained this several times. If you set up a websocket on a domain it can only be a websocket, and other stuff like .js files cannot be served on that domain. That's why I set up wss.citadel.helioho.st as the websocket so you could put a real website with .js files etc on citadel.helioho.st. You said "I like the sound of this better" so I wasted like 45 minutes of my time reconfiguring your account which was working perfectly fine to change the domains around for no reason other than you like the sound of it better.

Correct, if you allow Plesk to create SFTP accounts they aren't jailed properly which is a security vulnerability. Unfortunately Plesk doesn't allow any way for people to create FTP or FTPS accounts without also being able to create SFTP accounts. We can create additional FTP accounts for you if you need though.

I went ahead and created a full backup of all of your files which you can download from https://heliohost.org/backup/ if you need them prior to deleting anything.

Here is a detailed breakdown of your storage usage: Backups 0 MB Emails 1.89 MB Files 913.76 MB Trash 0 MB Logs 53.29 MB PSQL 0 MB MySQL 76.78 MB Total 1045.72 MB Here is the storage that the domain adjeometry.com is using: 0 /home/vamdesign.tk/adjeometry.com/cgi-bin 4.0K /home/vamdesign.tk/adjeometry.com/.well-known 34M /home/vamdesign.tk/adjeometry.com/Indusjob2 42M /home/vamdesign.tk/adjeometry.com/Indusjobold 4.0K /home/vamdesign.tk/adjeometry.com/Nooralshawq 576K /home/vamdesign.tk/adjeometry.com/familytree 276K /home/vamdesign.tk/adjeometry.com/lg-smart-font 34M /home/vamdesign.tk/adjeometry.com/metrixpms 3.7M /home/vamdesign.tk/adjeometry.com/nooralshawq 11M /home/vamdesign.tk/adjeometry.com/wp-admin 220M /home/vamdesign.tk/adjeometry.com/wp-content 54M /home/vamdesign.tk/adjeometry.com/wp-includes 422M /home/vamdesign.tk/adjeometry.com Here is the storage that the domain praanacosmos.com is using: 0 /home/vamdesign.tk/praanacosmos.com/cgi-bin 4.0K /home/vamdesign.tk/praanacosmos.com/.well-known 10M /home/vamdesign.tk/praanacosmos.com/wp-admin 102M /home/vamdesign.tk/praanacosmos.com/wp-content 49M /home/vamdesign.tk/praanacosmos.com/wp-content(org) 52M /home/vamdesign.tk/praanacosmos.com/wp-includes 247M /home/vamdesign.tk/praanacosmos.com Here is the storage that the domain vamdesign.tk is using: 0 /home/vamdesign.tk/public_html/cgi-bin 4.0K /home/vamdesign.tk/public_html/.well-known 0 /home/vamdesign.tk/public_html/adjeometry 142M /home/vamdesign.tk/public_html/praanacosmos 2.6M /home/vamdesign.tk/public_html/project1 0 /home/vamdesign.tk/public_html/tmp 96M /home/vamdesign.tk/public_html/wp 240M /home/vamdesign.tk/public_html/ It looks like the vamdesign.tk and praanacosmos.com domains aren't even hosted by us so maybe those files can be deleted? Also if you decide you need more than 1000 MB you can purchase up to 7000 MB storage yourself at https://heliohost.org/dashboard/storage/ If you decide to increase your storage you will be able to login again immediately without waiting for an admin to delete files for you.

Set.

Passenger is only needed if you want to make a Node.js website. A Node.js websocket does not need Passenger. Since you turned on Passenger I assumed you wanted to make a Node.js website, not a websocket on that domain, so I created a different domain for the websocket. I have disabled Passenger for you, deleted the wss subdomain, and made the citadel.helioho.st domain the websocket instead.

Since you set up Passenger on citadel.helioho.st I assumed you wanted to put a website on that domain, so I made another domain for the websocket. It doesn't really matter which port you use. If someone else comes along and tries to use port 8080 it will say it's already in use if your websocket is already running. If you stop your websocket and someone else starts using 8080 then you won't be able to start your websocket anymore.

Ok, I created the proxy to port 8080 on wss://wss.citadel.helioho.st and it seems to be working root@control [~]# ./websocat wss://wss.citadel.helioho.st hello ^C And the logs show this

I did notice these domains are trying to send emails despite the limit being 0. Want me to set the nilijua.xyz limit to 50 or can you figure out where the 9 emails came from first?

Ok, let's leave Passenger on for your main domain so you can play around with that. I created 2 subdomains for you: wss.citadel.helioho.st which we'll use for your websocket, and control.citadel.helioho.st that we'll use for your start/stop/logs index.sh script. The new domains should start working in about 100 minutes or so. You can go ahead and move the .htaccess file and index.sh file from /home/citadel.helioho.st/httpdocs/bot_control/ to /home/citadel.helioho.st/control.citadel.helioho.st/ We'll work on this more when the domains are ready.

No external ports are available, and we don't open them in the firewall on Morty, Tommy, or Johnny. Internal ports are basically all available, but they can't be accessed remotely without proxying them through Apache or Nginx because the firewall blocks the direct connection. There are 65535 internal ports, and only a handful are in use by other users. Right now Passenger is blocking access to everything on your domain, so we need to either add another subdomain to access /bot_control/ or you'll need to disable Passenger.

Switch to another port other than 3000. Obviously someone else is using 3000.

Instead of this Try this if [ "$QUERY_STRING" == "action=start" ]; then if [ $running -ne 0 ]; then echo "$bot_name is already running..." else echo "[$ts] Starting $bot_name." >> $pwd/$log_name /opt/plesk/node/22/bin/node /home/$main_domain/$bot_name >> $pwd/$log_name 2>&1 & echo "Starting $bot_name...<script>window.location.replace('/$control/');</script>" fi fi

Passenger automatically kills your Node.js server after 5-10 minutes without any page hits. That's why I was recommending starting and stopping your websocket with the /bot_control/index.sh script if you want it to run for more than 5 minutes.