Custom domain shows 404 error
When I open the link generated in the email, it shows the following error:
[404 error] If you're seeing this error after installing, check this FAQ for the fix: https://sendy.co/troubleshooting#404-error
I added the custom domain: track.mydomain.com and also added the CNAME to my Sendy URL:
track.mydomain.com CNAME sendy.mydomain.com
The sendy.mydomain.com domain is mapped to the Sendy Document Root path: public_html/sendy via virtual domain configuration
The track.mydomain.com domain is mapped to the Sendy Document Root path: public_html/sendy via virtual domain configuration. This way, when I open the track.mydomain.com domain, the Sendy login opens.
Additionally, I added extra settings to my .htcaccess file.
ErrorDocument 404 "[404 error] If you're seeing this error after install, check this FAQ for the fix: https://sendy.co/troubleshooting#404-error" Options +FollowSymLinks Options -Multiviews RewriteEngine On # --- Desenrollar los wrappers de SES (CL0, CL1, etc.) hacia los endpoints de Sendy --- # CLICS: .../CL0/https:%2F%2F<host>%2Fl%2F<e1>%2F<e2>%2F<e3>... RewriteRule ^CL[0-9]+/(https?)(?::|%3A)%2F%2F[^/]+%2Fl%2F([^/%]+)%2F([^/%]+)%2F([^/%]+).* /l.php?i=$2/$3/$4 [L,NE] # APERTURAS: .../CL0/https:%2F%2F<host>%2Ft%2F<e1>%2F<e2>... RewriteRule ^CL[0-9]+/(https?)(?::|%3A)%2F%2F[^/]+%2Ft%2F([^/%]+)%2F([^/%]+).* /t.php?i=$2/$3 [L,NE] # WEBVERSION: .../CL0/https:%2F%2F<host>%2Fw%2F<e1>%2F<e2>%2F<e3>(%2Fa)? RewriteRule ^CL[0-9]+/(https?)(?::|%3A)%2F%2F[^/]+%2Fw%2F([^/%]+)%2F([^/%]+)%2F([^/%]+)(?:%2F([aA]))?.* /w.php?i=$2/$3/$4$5 [L,NE] RewriteCond %{SCRIPT_FILENAME} !-d RewriteCond %{SCRIPT_FILENAME} !-f RewriteRule ^([a-zA-Z0-9-]+)$ $1.php [L] # Link tracker RewriteRule ^l/([a-zA-Z0-9/]+)$ l.php?i=$1 [L] # Open tracker RewriteRule ^t/([a-zA-Z0-9/]+)$ t.php?i=$1 [L] # Web version RewriteRule ^w/([a-zA-Z0-9/]+)$ w.php?i=$1 [L] # unsubscribe RewriteRule ^unsubscribe/(.*)$ unsubscribe.php?i=$1 [L] # subscribe RewriteRule ^subscribe/(.*)$ subscribe.php?i=$1 [L]
This discussion has been closed.
Comments
Hi,
Please ensure the .htaccess file in your Sendy directory is Sendy's original .htaccess file and it is not modified.
You can download Sendy from https://sendy.co/get-updated to compare the .htaccess with the one in your Sendy directory.
Best regards,
Ben