balloons

216.218.216.167 ??? where are you trying to connect? It's trying to connect to something unrelated to HelioHost. Also, HelioHost does not provide connectivity on port 22. (Excludes VPS)

Krydos and I have spoken on Discord and Krydos said they never recommend this. This seems to be the cause in my case. For the OS upgrade, you should sign a new VPS contract and move the domain. Then stop the old VPS.

I actually had the same experience a few days ago. After sudo reboot, I can't log in to ssh. (I already chose to terminated this vps, Please don't mind my support) https://discord.com/channels/398197622168616962/398538798994161664/1024134118222594129 A VPS that employs Ubuntu may experience this after a reboot. I used Ubuntu 20.04 LTS when I signed up for VPS, and then upgraded to Ubuntu 22.04 LTS. Also, I configured ufw a few days ago, so maybe there is a problem using ufw. Since Krydos was able to console login, it looks like the root admin can recover this.Posting here is fine.

Just to be sure, I confirmed this implication on Discord. https://discord.com/channels/398197622168616962/398538798994161664/1028106362821034034 Krydos says "Both update your last login date". This was not working with cPanel. Great update!

It may be helpful to include this URL in a bookmark or shortcut that you can easily find. https://heliohost.org/login/

HelioHost support emails will be sent to this HelioNet Email Support. However, there have been reports of it not arriving in transmissions from Gmail. Since you can post directly here. Or you can also use Discord.

Hi plp050452, From your previous post, I used Gmail, so I'm currently having problems transferring between HelioHost and Gmail. I see a new email address in your past post, so please wait for the root admin's response. Also, I understand your confusion, but please don't post in multiple places because of this. It annoys us to support.

Information I researched to share This is only blocking mail delivery from HelioHost to Gmail. No problem from Gmail to HelioHost. I could not confirm HelioHost registration on the official blacklist. This issue only affects Gmail. This also blocks emails sent by HelioHost to you. But don't panic if you've gotten HelioHost information outside of email! If you are forwarding mail from HelioHost to Gmail, it will also be blocked. Use POP instead. Presumably this block is a domain level block for heliohost.org and heliohost.org. If you are using a custom domain you may not be affected by the block. If you receive a notification of Plesk migration in the future, if that email address is Gmail, that email is currently blocked, so please change the notification email address. I had Gmail registered with HelioHost, so I was affected by this, but since I'm on Discord, I didn't have to rush to change my email address. Discord is the fastest for news and pinging me. If you're a regular user of HelioNet, don't panic as well, because there are alternatives to e-mail. Note that some servers may have different restrictions. (Especially Johnny)

hi c2itnow, If you used Gmail, recently HelioHost and Gmail's servers have been on bad terms. Note that support@heliohost.org will only reach the Email Support of this forum. If you use this forum, you may not get much benefit from email.

If you have access to your domain's nameservers, There is also a method of refusing to send and receive mail at the nameserver level. About receiving mail removes MX records. and sending mail adds the following TXT record (Assuming your domain is example.com) example.com TXT v=spf1 -all _dmarc.example.com TXT v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s; *._domainkey.example.com TXT v=DKIM1; p=

I communicated that concern to Krydos on Discord last year. I think it happened at a fairly early stage. https://letsencrypt.org/docs/rate-limits/ If you need specific steps to issue an alternative certificate, we may be able to show you the steps. It can be dealt with in Plesk's control panel.

I use Hugo for blogging. You will find it very convenient to post your blog this way, especially if you are accustomed to working with CLI aka commands.

I'm hearing about yashrs from Krydos. Because you are involved in server work these days. Thank you for your support as a VPS admin. Krydos set up my VPS. It was just after the tragedy of losing cPanel. Still thank you for dealing with my VPS. I see the day when your Plesk work is complete and your server can be built. I can always meet you on Discord. Jenova is always a quick response. I know you are an excellent Moderator. The VPS I lost will be assigned to someone. It will continue to support HelioNet and HelioHost. I'm still using Tommy server and will get Plesk soon, but want to get a better US server on HelioHost so I'll act later. I am grateful for the response so far and for meeting you.

Unfortunately I need to ask the VPS admin to do the shutdown work. My VPS: vps35.heliohost.us This VPS adopts Rocky. Rocky upgraded many packages a few hours ago. I can't connect to ssh after updating this package. Normally I should ask for a VPS reboot, but I was considering shutting down the VPS, This was a good time to shut down the VPS. I am considering using Morty instead of this VPS in the future. (I have to wait a while for Morty to be released) Or I may sign up for a VPS again in the future. Krydos and a few moderators at Discord led me to HelioHost VPS. It provided me with a great experience. I am grateful to meet the staff at HelioHost and everyone who uses it.

This examples here is port 80. It is the standard port for http. The standard port for https using SSL is 443. Keep this in mind if you have referenced and configured this example. It will be necessary to add the setting of Apache. You also need to specify the location of Let’s Encrypt issued with this setting. My VPS (Rocky instead of CentOS) uses Caddy instead of Apache to simplify these configurations. Caddy is a web server and supports Let’s Encrypt (or ZeroSSL) issuance and automatic updates. Since you have selected CentOS, The EOL for CentOS 8 is December 31, 2021: https://blog.centos.org/2020/12/future-is-centos-stream/

A certificate is always required for https (SSL). cPanel issued own certificate "AuroSSL". Now this is dead so the certificate will not be renewed. Therefore the certificate has expired. That is the cause of this problem. This workaround is what we have answered so far. If you need it right away. Or you can wait for the Plesk installation to complete. Plesk could provide the issuance of SSL certificates. I moved the website running on my custom domain to HelioHost VPS to work around this issue. VPS can also choose the method of issuing the SSL certificate.

If you want to resolve it, issue an SSL certificate such as ZeroSSL, upload it to your user directory (Other than public_html) via SFTP and comment it.

It seems that the entire HelioHost VPS is down. (Currently my VPS is also down) I was able to confirm this situation from Discord. VPS admin is working on this recovery. My VPS got a response. When you see this, your VPS will be able to connect.

Recently Google has begun to apply deleting data from accounts that haven't been used for two years. https://support.google.com/googleone/answer/10214036 There are several alternative storage services, but they all have their limitations. Provider company, country, etc. There is also the possibility of service outages. That's true even if you're using a domain. Even .com has a registrar and a registry (VeriSign). It is under the jurisdiction of US law. The workaround would be to save it to your local PC or smartphone.

If I use speedtest.net:

It will be an opportunity to see the changes of the times. Even during this period, our internet environment changed. My workplace was a 1Gbps line last year (2020). This measurement date was Sunday, so it is a day with a lot of line sharing.

Since you have set "~all", In this case, some mail servers such as Google Workspace will be passed. This is a consideration if you forget to add a server to your SPF configuration. https://support.google.com/a/answer/10683907 If you obviously refuse to send mail from other servers, you can use "-all" instead.

I checked your server with dig. $ dig infantex.com.mx txt ;; ANSWER SECTION: infantex.com.mx. 300 IN TXT "v=spf1 include:_spf.google.com ~all" TXT records only return SPF. There is no DMARC. Something is wrong with the record settings. Please note that the SMTP server also processes the received mail. Putting incoming mail into a mailbox is the work of SMTP, and receiving from the mailbox is the work of POP or IMAP.

Include it in the TXT record of the name server for your domain. You should be able to get enough information on this by searching SPF or DMARC on Google. Free Google Apps account is currently Google Workspace, but it works as long as there is no domain change. Therefore, the Google Workspace documentation can also be a solution tip.