Wrong domain name when using Alias (DirectAdmin)

[Noaber]

Bug description

When using the plugin it's generating a sitemap.xml.
Awesome, however if I look into the sitemap.xml I see all links with domainA.eu.
This is the original url in DirectAdmin, but the site is available online as DomainB.eu (this is the alias in DirectAdmin).
This domainB.eu is also in the laravel .env.

I looked into the config, but I can not set the domain url. So where is the domain fetched from ?

Steps to reproduce

Make a Directadmin domain (domainA) and make a alias (domainB).
Set Laravel .env to use domainB as app url and goto sitemap.xml (you see domainA in the xml instead of domainB).

Environment and versions

APP_NAME="My Site"
APP_ENV=production
APP_KEY=bxxxxxx
APP_DEBUG=false
APP_URL=https://domainB.eu

Additional details

No response

[martyf]

A few things for you to look at please.

Firstly, what is the Site configured as within Statamic? By default should be "/" which means Sitemapamic will fall back to the config('app.url'), which for you should be domainB

Secondly, after changing your config, did you clear Sitemapamic's cache? See the docs for more details.

Is your setup multi-site, or just a single site?

[Noaber]

Hello @martyf,

Thanks for your quick reply. The Statamic site is a single site (just has a domain pointed to it using DirectAdmin).
I see a / on the settings (see screenshot, sorry for the Dutch)

APP_URL = pointed to domainB
I also tried the clear cache as you described and now I have the correct domain in the sitemap.xml.

However I thought it was working before, then suddenly not. I will keep an eye on this, for now it seems to be correct!

[martyf]

If you view the sitemap, then change config (or access) it will be cached. You do need to clear the cache after changes are made. When content gets saved, that should clear the cache automatically. Does this solve the issue?

[Noaber]

Mhhh, its wrong again (sitemap is showing now domainA again).
What I did was generating a new release (using DeployerPHP) to fix a ux bug. Yesterday before the deploy it was correct, after the deploy its domainA again. The deploy script actions are

task('deploy', [
    'deploy:prepare',
    'deploy:vendors',
    'build:assets',
    'artisan:storage:link',
    'artisan:optimize:clear', // clear stale caches
    'artisan:optimize',       // generate new optimizations
    'artisan:migrate',
    'statamic:stache:clear',
    'statamic:stache:warm',
    'stache:refresh',
    'deploy:symlink',
    'deploy:unlock',
    'deploy:cleanup',
]);

Also when a user makes a new entry (page, news item etc) then I would guess Statamic will clear the cache.

Another thing just came in mind, also domainA is accessible, so you said that the sitemap is being cached.
If someone (user or bot) access domainA first, then it will generate the sitemap.xml and visiting from domainB will show domainA in the sitemap.xml, correct ?

[martyf]

Your deploy script should also have statamic:sitemapamic:clear in it - that will clear Sitemapamic's caches on deploy.

If both are aliases of each other, only one primary domain should appear in the sitemap.xml, regardless of where it is coming from. This is a limitation of the current implementation.

A major update to Sitemapamic is coming, I just don't have an ETA at this stage.

[Noaber]

Thanks for the reply and awesome to hear about the major update. Looking forward to it.

I will add the statamic:sitemapamic:clear to the deploy script.
As for the domains. Problem is that domainA is the "primair" domain, however domainB is used (yeah I know, weird configured by the hoster) and that domainB is always used in the sitemap.xml

But after clearing the cache, I understand that the first hit is caching the sitemap.xml. So if the first hit comes from domainA, this will be set in the sitemap.xml, would the first hit be from domainB, then that will be used in the sitemap.xml

[martyf]

Yes, that is correct in its current state.

You could always include something in your domain to attempt to render it on domain A at deploy time (and also as the sitemap gets saved).

Is this issue OK to close now?

[Noaber]

Yes, I understand. It’s likely a combination of the current plugin (eager for the rewrite! :) ) and the hosting configuration being set up weirdly. (and ofcourse close this issue)