Krydos

Nice! Glad you got it figured out.

Yes, if the domain is hosted on the server Plesk doesn't even bother looking at the MX records or anything and just sends it internally. You would have to make a temporary email address on a domain that isn't hosted on Plesk to make the email leave the server, and then you could forward from the temporary email back to an infantex.com.mx address. Couldn't you create the email address on Plesk and then have your gsuite log in to Plesk and download the emails? That seems easier.

No, you're making progress. Check out the log now. Jul 15 05:16:38 tommy2 postfix-local[101248]: C09F3402A61D: dmarc: stderr: PASS Jul 15 05:16:38 tommy2 postfix-local[101248]: cannot chdir to mailname dir jazc: No such file or directory Jul 15 05:16:38 tommy2 postfix-local[101248]: C09F3402A61D: Unknown user: jazc@infantex.com.mx Jul 15 05:16:38 tommy2 postfix/pipe[101242]: C09F3402A61D: to=<jazc@infantex.com.mx>, orig_to=<info@infantex.com.mx>, relay=plesk_virtual, delay=0.58, delays=0.2/0.17/0/0.21, dsn=2.0.0, status=sent (delivered via plesk_virtual service) Jul 15 05:16:38 tommy2 postfix/qmgr[121784]: C09F3402A61D: removed That email address it's trying to deliver to doesn't exist in Plesk. Try creating it.

I still see this "Jul 15 05:06:11 tommy2 dmarc[87197]: 5E302402C20C: SPF record was not found in Authentication-Results". It doesn't like your SPF record. Maybe try setting your SPF to "v=spf1 ip4:65.19.141.197 +ip4:65.19.141.77 +ip6:2001:470:1:1ee::2002 include:_spf.google.com ~all"

Yeah, copy/paste the Plesk data in. You can have multiple TXT records for DKIM if you send from your VPS, Google, and Plesk, etc. Each source needs it's own unique DKIM. I have no idea why MailGenius is saying that. I even looked at the report you linked and their own report shows the reverse DNS for tommy2.heliohost.org correctly.

We're happy to announce that new account signups are beginning today. One year ago today without any warning we lost our cPanel licenses that we had been using for over 16 years. HelioHost has been through good times and bad, and the last year is definitely the worst we've experienced. We're coming back bigger and better than ever though. Starting today we will be sending out invites to create a new account on Plesk starting with our biggest donors over the last two years. You can check your ETA and check the current number of invites we are sending out each day at https://www.heliohost.org/eta/ If you're not on the list let us know and we can add you. We will be sending out only 1 invite per day for a few days to make sure everything is working, and then we will increase the number of invites each day as everything gets tested. A huge thanks goes out to all of our donors who have kept HelioHost alive through the last year.

Reverse DNS is set up correctly for Tommy2 for both IPv4 and IPv6 root@cody [/home/krydos]# dig +noall +answer -x 65.19.141.77 77.141.19.65.in-addr.arpa. 4798 IN CNAME 77.subnet72.141.19.65.in-addr.arpa. 77.subnet72.141.19.65.in-addr.arpa. 4835 IN PTR tommy2.heliohost.org. root@cody [/home/krydos]# dig +noall +answer -x 2001:470:1:1ee::2002 2.0.0.2.0.0.0.0.0.0.0.0.0.0.0.0.e.e.1.0.1.0.0.0.0.7.4.0.1.0.0.2.ip6.arpa. 14400 IN PTR tommy2.heliohost.org. Here's your error log now Jul 14 19:54:21 tommy2 plesk-sendmail[2071]: S2070: py-limit-out: stderr: INFO:__main__:Setting 'X-PPP-Vhost' header to 'infantex.com.mx' Jul 14 19:54:21 tommy2 plesk-sendmail[2071]: S2070: py-limit-out: stderr: PASS Jul 14 19:54:21 tommy2 plesk-sendmail[2071]: S2070: check-quota: stderr: SKIP Jul 14 19:54:21 tommy2 postfix/pickup[128820]: B25E940B7FF6: uid=10183 from=<infantx@infantex.com.mx> Jul 14 19:54:21 tommy2 postfix/smtpd[1676]: warning: hostname net6-ip230.linkbg.com does not resolve to address 87.246.7.230: Name or service not known Jul 14 19:54:21 tommy2 postfix/smtpd[1676]: connect from unknown[87.246.7.230] Jul 14 19:54:21 tommy2 postfix/cleanup[128127]: B25E940B7FF6: message-id=<cb96865d9dfaa51f3a09c30ba074aa45@infantex.com.mx> Jul 14 19:54:21 tommy2 postfix/qmgr[15698]: B25E940B7FF6: from=<infantx@infantex.com.mx>, size=2984, nrcpt=1 (queue active) Jul 14 19:54:21 tommy2 postfix-local[2090]: B25E940B7FF6: from=<infantx@infantex.com.mx>, to=<infantx@infantex.com.mx>, dirname=/var/qmail/mailnames Jul 14 19:54:21 tommy2 spamd[32163]: spamd: connection from localhost.localdomain [::1]:40084 to port 783, fd 6 Jul 14 19:54:21 tommy2 spamd[32163]: spamd: using default config for infantx@infantex.com.mx: /var/qmail/mailnames/infantex.com.mx/infantx/.spamassassin/user_prefs Jul 14 19:54:21 tommy2 spamd[32163]: spamd: processing message <cb96865d9dfaa51f3a09c30ba074aa45@infantex.com.mx> for infantx@infantex.com.mx:30 Jul 14 19:54:22 tommy2 spamd[32163]: spamd: clean message (0.2/7.0) for infantx@infantex.com.mx:30 in 0.4 seconds, 3063 bytes. Jul 14 19:54:22 tommy2 spamd[32163]: spamd: result: . 0 - HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,NO_RELAYS,T_SCC_BODY_TEXT_LINE scantime=0.4,size=3063,user=infantx@infantex.com.mx,uid=30,required_score=7.0,rhost=localhost.localdomain,raddr=::1,rport=40084,mid=<cb96865d9dfaa51f3a09c30ba074aa45@infantex.com.mx>,autolearn=no autolearn_force=no Jul 14 19:54:22 tommy2 postfix-local[2090]: B25E940B7FF6: spam: stderr: PASS Jul 14 19:54:22 tommy2 dk_check[2095]: B25E940B7FF6: DKIM Feed: No signature Jul 14 19:54:22 tommy2 postfix-local[2090]: B25E940B7FF6: dk_check: stderr: PASS Jul 14 19:54:22 tommy2 dmarc[2096]: B25E940B7FF6: SPF record was not found in Authentication-Results Jul 14 19:54:22 tommy2 spamd[84024]: prefork: child states: II Jul 14 19:54:22 tommy2 dmarc[2096]: B25E940B7FF6: DMARC: smtpdomain=infantex.com.mx maildomain=thankyou.com mailfrom=no@thankyou.com stamp=1657828462 ip=unknown adkim=relaxed aspf=relaxed p=REJECT sp=UNSPECIFIED pct=100 align_dkim=fail align_spf=fail spfres=unknown dkimres=unknown dmarccheck=DMARC_POLICY_REJECT dmarcstatus=STOP Jul 14 19:54:22 tommy2 postfix-local[2090]: B25E940B7FF6: dmarc: stderr: STOP Jul 14 19:54:22 tommy2 postfix-local[2090]: message discarded by a mail handler Jul 14 19:54:22 tommy2 postfix/pipe[2089]: B25E940B7FF6: to=<infantx@infantex.com.mx>, orig_to=<info@infantex.com.mx>, relay=plesk_virtual, delay=0.7, delays=0.06/0.04/0/0.61, dsn=2.0.0, status=sent (delivered via plesk_virtual service) Jul 14 19:54:22 tommy2 postfix/qmgr[15698]: B25E940B7FF6: removed Try using this as your SPF "v=spf1 ip4:65.19.141.197 +ip4:65.19.141.77 include:_spf.google.com ~all" The other issue I see is you don't have DKIM set up. In Plesk mail section enable DKIM and then copy/paste the TXT records they give you into Cloudlfare.

Thank you for the very generous donation. You have been sent an email with a link which when clicked will move your account to Plesk. After the link is clicked there will be a second email when your account is ready to be logged in to, and instructions on how to login. Thanks again.

Here's the log for your contact form. Jul 14 02:38:20 tommy2 plesk-sendmail[48064]: S48062: py-limit-out: stderr: INFO:__main__:Setting 'X-PPP-Vhost' header to 'infantex.com.mx' Jul 14 02:38:20 tommy2 plesk-sendmail[48064]: S48062: py-limit-out: stderr: PASS Jul 14 02:38:21 tommy2 plesk-sendmail[48064]: S48062: check-quota: stderr: SKIP Jul 14 02:38:21 tommy2 postfix/pickup[44550]: 23602401FAEE: uid=10183 from=<infantx@infantex.com.mx> Jul 14 02:38:21 tommy2 postfix/cleanup[45317]: 23602401FAEE: message-id=<1ae95ef6ce2de4bc3179c9c8515f7197@infantex.com.mx> Jul 14 02:38:21 tommy2 postfix/qmgr[28715]: 23602401FAEE: from=<infantx@infantex.com.mx>, size=2985, nrcpt=1 (queue active) Jul 14 02:38:21 tommy2 postfix-local[48103]: 23602401FAEE: from=<infantx@infantex.com.mx>, to=<infantx@infantex.com.mx>, dirname=/var/qmail/mailnames Jul 14 02:38:21 tommy2 spamd[9978]: spamd: connection from localhost.localdomain [::1]:40948 to port 783, fd 6 Jul 14 02:38:21 tommy2 spamd[9978]: spamd: using default config for infantx@infantex.com.mx: /var/qmail/mailnames/infantex.com.mx/infantx/.spamassassin/user_prefs Jul 14 02:38:21 tommy2 spamd[9978]: spamd: processing message <1ae95ef6ce2de4bc3179c9c8515f7197@infantex.com.mx> for infantx@infantex.com.mx:30 Jul 14 02:38:21 tommy2 spamd[9978]: spamd: clean message (0.2/7.0) for infantx@infantex.com.mx:30 in 0.4 seconds, 3064 bytes. Jul 14 02:38:21 tommy2 spamd[9978]: spamd: result: . 0 - HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,NO_RELAYS,T_SCC_BODY_TEXT_LINE scantime=0.4,size=3064,user=infantx@infantex.com.mx,uid=30,required_score=7.0,rhost=localhost.localdomain,raddr=::1,rport=40948,mid=<1ae95ef6ce2de4bc3179c9c8515f7197@infantex.com.mx>,autolearn=no autolearn_force=no Jul 14 02:38:21 tommy2 postfix-local[48103]: 23602401FAEE: spam: stderr: PASS Jul 14 02:38:21 tommy2 dk_check[48118]: 23602401FAEE: DKIM Feed: No signature Jul 14 02:38:21 tommy2 postfix-local[48103]: 23602401FAEE: dk_check: stderr: PASS Jul 14 02:38:21 tommy2 dmarc[48119]: 23602401FAEE: SPF record was not found in Authentication-Results Jul 14 02:38:21 tommy2 dk_check[48118]: 23602401FAEE: DKIM Feed: No signature Jul 14 02:38:21 tommy2 postfix-local[48103]: 23602401FAEE: dk_check: stderr: PASS Jul 14 02:38:21 tommy2 dmarc[48119]: 23602401FAEE: SPF record was not found in Authentication-Results Jul 14 02:38:21 tommy2 dk_check[48118]: 23602401FAEE: DKIM Feed: No signature Jul 14 02:38:21 tommy2 postfix-local[48103]: 23602401FAEE: dk_check: stderr: PASS Jul 14 02:38:21 tommy2 dmarc[48119]: 23602401FAEE: SPF record was not found in Authentication-Results Jul 14 02:38:21 tommy2 dmarc[48119]: 23602401FAEE: DMARC: smtpdomain=infantex.com.mx maildomain=thankyou.com mailfrom=no@thankyou.com stamp=1657766301 ip=unknown adkim=relaxed aspf=relaxed p=REJECT sp=UNSPECIFIED pct=100 align_dkim=fail align_spf=fail spfres=unknown dkimres=unknown dmarccheck=DMARC_POLICY_REJECT dmarcstatus=STOP Jul 14 02:38:21 tommy2 postfix-local[48103]: 23602401FAEE: dmarc: stderr: STOP Jul 14 02:38:21 tommy2 postfix-local[48103]: message discarded by a mail handler Jul 14 02:38:21 tommy2 postfix/pipe[47528]: 23602401FAEE: to=<infantx@infantex.com.mx>, orig_to=<info@infantex.com.mx>, relay=plesk_virtual, delay=0.69, delays=0.06/0.01/0/0.62, dsn=2.0.0, status=sent (delivered via plesk_virtual service) Jul 14 02:38:21 tommy2 postfix/qmgr[28715]: 23602401FAEE: removed Your SPF is "v=spf1 include:_spf.google.com ~all" which doesn't include 65.19.141.77, so since Tommy isn't authorized to send emails the message is discarded. You can fix this by allowing Tommy to send emails for your domain.

993 is IMAP. I prefer IMAP because you get your emails quicker. Yeah, use ns1.heliohost.org and ns2.heliohost.org or turn off proxying in Cloudflare.

Not being able to connect to IMAP, and SMTP on the tommy2.heliohost.org domain was my fault. Apparently the server was using a self-signed certificate. I set up email with a real SSL certificate and now it should work. SMTP host: tommy2.heliohost.org SMTP port: 465 SMTP SSL/TLS: on IMAP host: tommy2.heliohost.org IMAP port: 993 IMAP SSL/TLS: on

Cloudflare is the problem. When your mail client tries to connect to SMTP or IMAP it's looking at the A record for zaldivar.mx and it gets 172.67.139.59 and 104.21.79.5, and then it tries to connect to port 995 or 465 or whatever on those Cloudflare servers and it times out. There's a few easy ways to fix it. I recommend just typing tommy2.heliohost.org into your mail client rather than zaldivar.mx. That's the easiest way to make it work. The other option if you really need to hide the server that you're on is you could create a subdomain like smtp.zalivar.mx and imap.zaldivar.mx or mail.zaldivar.mx or whatever and have Cloudflare give 65.19.141.77 as the A record. The third option is to switch to ns1.heliohost.org and ns2.heliohost.org instead of using Cloudflare, but then you would have to make a support request each time you needed your DNS changed. Eventually we will implement the ability to edit DNS records on your own.

The email address that you created your hosting account with is on a freenom .ga domain. It looks like you changed your forum email address to a gmail though, so I'll update your hosting account to use the same email. You should have received a new email with a link. Click the link and your account will be moved to Plesk.

@esn024 You asking about your position in line to be moved to Plesk was more or less on topic for this news post, but the best place for Customer Service requests like SSL and why is Wordpress not working have been moved to

Your SSL certificate got issued for thebrooksreflections.com but not for wwwthebrooksreflections.com. I reissued the SSL certificate for you so it will cover both. You could have done this yourself by going to Websites & Domains > thebrooksreflections.com > SSL/TLS Certificates > Reissue Certificate and then checked the box next to www. The reason your Wordpress stopped working is because you were using esn024 as your MySQL user. On cPanel if you used your username you could access all of your databases will full access. Plesk is a little more secure, and you have to actually grant permission to each database. What I recommend doing is creating a MySQL user named 'esn024_wp' or something like that and granting that new user access to just the Wordpress database. Make sure you update the wp-config.php file to match the new user and password. It's actually pretty insecure and bad practice to use a MySQL user that has full access to all of your databases for something like this. Wordpress is the most easily hacked software you can possibly install, and if someone gets a hold of the password that can access all of your databases on the whole account they can do that much more damage and not be contained to just Wordpress. If you can't figure out how to create a MySQL user and grant them access to your database let us know and we can help some more.

Yep, that donation counts for the Plesk transfer. You've moved from #960 to #1. You should have received an email with a link that allows you to move to Plesk. Let us know if you didn't get the email, or if you have any questions.

Yes, even though we don't have a functional control panel on cPanel anymore we have kept everyone's websites online during the transition. AutoSSL requires a cPanel license though so we've been installing SSL for people manually. If you want to get rid of the security warnings you can go to https://zerossl.com/ and create a free 90 certificate. Then upload the .zip file to /home/esn024/, but don't upload it to public_html. Let us know once it's uploaded and we can install it for you. If you don't like ZeroSSL for some reason you can pick any free certificate you want. We just recommend ZeroSSL because it's the easiest. Regarding the donation, can you find a transaction ID or anything so we can look it up? If the donation was made after 2020-07-14 it counts towards your Plesk ETA and we may be able to get you moved over immediately.

Oops, I already refunded the second payment before I read this post. The problem is PayPal is telling us one number before the transaction, and then telling us a different number after the transaction. It worked for years where PayPal would tell us the same number before and after, but a few months ago we noticed that it wasn't reliable anymore. I've made some changes to the website that should fix this issue. I'll make the new code live before much longer, but your payment went through on the old code.

No, 65.19.143.6 is the old cPanel server. Only one server can use an IP address at a time so Plesk is using 65.19.141.77. Normally when we rebuild a server we shutdown the old server and then rebuild it on the same IP, but since we wanted to have both online at the same time we had to do it this way.

Removed. Is this an adsense ad or something?

There you go https://www.heliohost.org/vps/pay/?code=Vg9WFIP3qfSZtsli

You've been sent an invite to move to Plesk for your existing Tommy account. Let us know if you haven't received the email.

The redirect has been removed. You may need to clear your browser cache to get the cached redirect to go away too. The better way to handle this for free is to go to https://zerossl.com/ and create a 90 SSL certificate. Then use SFTP to upload it to /home/dqdang. Don't upload it to public_html. Let me know once it's uploaded and I can install it for you. Then once you have working SSL you can use .htaccess to redirect to SSL again. The even better way to handle this is to get moved to Plesk. We're not moving any free accounts right now because it wouldn't be fair to the donors who don't have Plesk accounts yet if free people filled up the server before they even got an account, but if you donate as little as $1 for an existing account you can get moved to Plesk within 24 hours. You can check out https://www.heliohost.org/eta/?u=dqdang for your position as a free account. We're hoping to get new account creation fully tested soon and get the queue moving again.

I did a Wordpress files checksum and it said that none of the files had been modified. I reinstalled the core Wordpress files anyways, and hit the refresh button and your Wordpress install is no longer quarantined. It might have just been a fluke that it timed out like that. The load on Tommy is extremely low so I can't see why it would time out, unless Apache was restarting maybe. Anyways, it says Wordpress is good again now. Thanks for letting us know about that. It's actually pretty cool that Plesk detects hacked sites like that.

What I would do is log into webmail and on the left click settings, then click filters, and create a filter that deletes all email before it even enters the inbox.