Scheduler Laravel 5.2

Question

Scheduler Laravel 5.2

Navigation

#1 by (1 votes)

0

Good evening. I use the Scheduler of Laravel 5.2 to send emails and now I have a problem. Until Friday I was able to send signature emails in img normally, but on Friday night we migrated our servers and started using PHP 5.6.9 (former was 5.5.9 ), then signed emails are no longer sent. Can anyone help me?

Page code:

<html>
    <head></head>
    <body>
        Bom dia.<br>
        Seguem anexos os relat&oacute;rios de tempos an&aacute;liticos e desempenho dos operadores da sua equipe em rela&ccedil;&atilde;o ao dia anterior.<br>
        Qualquer d&uacute;vida favor entrar em contato com a equipe de estrat&eacute;gia.<br><br>

        <img src="<?php echo $message->embed('https://intranet.goesnicoladelli.net/imagens/assinatura_intranet.png'); ?>">
    </body>
</html>

Error reported when running CRON

[Swift_IoException]  Unable to open file for reading [https://intranet.goesnicoladelli.net/imagens/assinatura_intranet.png]

php laravel scheduler

asked by anonymous 27.02.2018 / 22:18

1 answer

Uncaught ReferenceError: angular is not defined Picking category from a table in Mysql

score 1 · Accepted Answer

The problem is that the code is trying to capture the " link " image, but its address is invalid .

curl -I https://intranet.goesnicoladelli.net/imagens/assinatura_intranet.png

curl: (60) SSL certificate problem: self signed certificate
More details here: https://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.

The problem is in the HTTPS connection, because the certificate is invalid.

To fix you need the valid address or download it and turn it into base64