Question cname server response error

[master58]

Server operating system version

Ubuntu 20.04.5LTS

Plesk version and microupdate number

Plesk Obsidian

Hello I have a problem.

To start, I use:

Ubuntu 20.04.5LTS
Plesk Obsidian
Cloudflare.

Well, I have an autoresponder tool installed, to send emails.

I want to add a custom addon domain, to track with another domain; They ask me to add a cname that points from track.domain.com to responder.com, which I have already done.

But the server does not respond or does the corresponding redirection and this comes out

 

[master58]

I was given this information What tracking and sending domains actually are? | The MailWizz KB

But I don't know where I should edit, if any php file for example; since I don't have to modify the tool itself, but something in plesk; or a dedicated address for it; but I don't know if it works.

 

[Kaspar]

View attachment 21784

Can you describe as detailed as possible what actions you performed in Plesk before you got the 404 error?

 

[master58]

Basically the application is installed in the application.com (of my property)

So I have another domain called company.com.

Both work fine with no issues. However, in the application they give me the option to create a custom tracking; so it is only enough to create a dns record of the cname type from track.company.com that points to application.com, which I have already created, in cloudflare, and even also in the dns administrator of the domain in plesk.

However, an additional configuration is missing in plesk, so that this tracking redirection is taken, modify for example apache's httdocs, php or something similar; I want to know if this is it; otherwise I will have to require a dedicated IP for the domain application.com

 

[Kaspar]

Basically the application is installed in the application.com (of my property)

Is application.com a domain you are hosting in Plesk? Or an external service?

Both work fine with no issues. However, in the application they give me the option to create a custom tracking; so it is only enough to create a dns record of the cname type from track.company.com that points to application.com, which I have already created, in cloudflare, and even also in the dns administrator of the domain in plesk.

Ok, great.

However, an additional configuration is missing in plesk, so that this tracking redirection is taken, modify for example apache's httdocs, php or something similar; I want to know if this is it; otherwise I will have to require a dedicated IP for the domain application.com

What additional configuration is missing?

 

[master58]

Is application.com a domain you are hosting in Plesk? Or an external service?


Ok, great.


What additional configuration is missing?

All domains are in plesk, on the same server.

They tell me I need this:

you need to make sure the server understands what to do when the request comes in for that cname, i.e. it must have the instructions for the correct redirect into that directory and after that path with wildcard.
You can have as many apps as you wish on that IP, but both the above must work (so that the server replies with the correct pages for each).
To test, just put in the cname, and it should arrive at the customer login screen.

But if I try track.company.com, it shows me the plesk login and not the information indicated, so what is missing is something to modify in the plesk configuration and that is where the problem is

 

[mow]

All domains are in plesk, on the same server.

All domains? Or is track.company.com missing? If so, you need to add that domain in plesk as a redirect to application.com.

 

[Kaspar]

The suggestion from @mow is interesting. And although your setup isn't entirely clear to me, I don't think you're looking for a redirect (or are you?). Instead I suspect you need to add track.company.com as an alias to application.com (without redirect). At least that would make more sense to me if you've already added a cname track.company.com that points to application.com. That way the server actually knows where to route requests to for track.company.com.