Havouza

But these two lines are identical

@datakick I get the attached error when trying to upgrade the php from 7.4 to 8.3. I understand that it is a probem with a module in the theme. There is perhaps more but must test to start somewhere and see if it is possible Any hints please, shop_error.txt

Yea I did decrypt it but attached wrong file

Problem Solved. Curl was not installed on the new server for some reason

@datakick Someone can interpret this decrypted 500 error. Se attachment exception_202532217170.txt

I have created an account on Google merchant. After crawling is say that product images is to small and must be 100x100 or bigger. But all images is made from 800x800 images. Anyone knows which image Google look at. The small_default is 98x98. Can it be that problem

Have looked thru them. Problem is that not one of them state what php version they support

Everything we use in modules manage php 8, its just the theme that don't. As I read your answer PS 1.7 and 8.x themes can work with TB?

We run the latest version of TB. It rund php7.4 because it seems there is some modules that cant handle php8. It seems that the Theme is the problem. I know there is no TB themes but before PS themes worked. Now PS has no 1.6 themes anymore and I assume 1.7 and 8.x does not work. Am I correct?

Ok I copies from another one and changed the content THANKS for the help. Not something simple really

Can I just create an empty new_order.txt

That does not exist in any mails folder

seems ok new_order.html

@datakick It is not translated but it is present in the mail folder for the shop language swedish. So at least it should be sent. It exist both in the root mail folder and in the theme mail folder. More suggestions please

@datakick I just noticed that the change say ssl. SSL is really depreaced so we use TLS. But perhaps it does not matter, it mostly a name change

I have implemented the code but I doubt it is the problem. Php Mailer already handle the certs correct. And I assume the mail alerts should use the PhpMailer also so it is something else that doesnt work

@datakick Late answer Its very common when you have many domains on your mailserver that you create one cert for all the domains by making lets encrypt create the same cert for multiple domains. its nothing that compromize security but when you get 20-30 domains on the email server it a pain in the but to keep track of all the different serts if you create them one by one. The problem here seems not to be the same. The php mailer works without a problem sendig out mails to customers, but the mail alerts, which I assume also use Php Mailer does not. So hardly the cert cant be the problem I will test the code change

I cant remember any code change datakick have done. Cant find that post

@the.rampage.rado Ok thanks that sorted out that problem. Now all mails to the customer works. BUT. The admin mail still not work for some reason. There is not much to configure in the mail nocice module more than email address and I have put 2 there just to be sure. And if the PHP Mailer module now is correct configured, the admin mail should also work but nothing. And nothing in any log that I can find. I have also checked the mail.log from the mail server but nothinng

We get this error when testing mail. So who is the sender? The customer service email address and the smtp username is same so who is the sender? Recipient address rejected: Sender is not same as SMTP authenticate username

Not much to misconfigure in the php mailer. And still it works everywhere except tb.

Just one more thing. We also have an opencart shop with 7 services we sell. The contact for on that shop which is a virtual domain on the same server as TB use exactly the same settings and works flawless. The mail arrive 10 sec after I press the send button

and that old post has no meaning for our problem. And still I dont understand why it works everywhere else with the exact same settings

@datakick my hosting provider is a dedicated server over wihich I have 100% control. The second dedicated server we have is our own email server with postfix and dovecot. I have 100% control on that also. So your assumtion is totally wrong

We still have mail problems When trying to send a testmail iI get this error Failed to send email: SMTP Error: Could not connect to SMTP host. Connection failed. stream_socket_enable_crypto(): Peer certificate CN=`mail.mxmail.pro' did not match expected CN=`mail.jv80.se' The smtp host is fully working I can use it with both webmail and the mail client I dont know where it get mail.mxmail.pro from, the smtp server used is mail.jv80.se