Polishing after domain migration

ℹ️ Support
1

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • 30.0.6
  • Operating system and version (e.g., Ubuntu 24.04):
    • Gentoo linux
  • Web server and version (e.g, Apache 2.4.25):
    • Apache 2.4.63
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • none
  • PHP version (e.g, 8.3):
    • 8.2.28
  • Is this the first time you’ve seen this error? (Yes / No):
    • as far as I can tell
  • When did this problem seem to first start?
    • after successful domain migration
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • Gentoo package (basically raw untar)
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • no

Summary of the issue you are facing:

I recently migrated to a different domain. The switch itself was painless however it seems that at the very least some clients don’t like it. I read a number of AH02032: Hostname www.a.b.c provided via SNI and hostname www.z.b.c provided via HTTP have no compatible SSL setup in apache error log, however the errors would NOT be nearly enough if all clients were still using the old URL. In fact the client on my PC has updated its own configuration after detecting the permanent redirect to the new domain.

Is it possible that some very outdated clients are generating these warnings? I consider them as warnings because I have no support tickets for missing access to nextcloud. If so, should this problem solve itself as clients update and self-correct their configuration?

Another point is that a huge number of references to the old domain persist in the database. While some are to be expected (old emails, contacts…) I wonder if any of those may create problems in the future, howeve my (lack of) knowledge of the database structure and logic makes it impossible to take action.

2

Regarding the domains, if you create permanent redirects to the new one, the clients should update the domains in their connection (in contrast to temporary redirects).

For the database, is the domain in different places there?

3

Thanks for the reply.

The redirects are permanent and as I said at least my client has updated its own configuration.

The database is on localhost, as it’s always been, if that’s what you are asking.
The old domain is found in a lot of records in several tables of the database, for example activity and cards. While activity is not concerning as it’s probably just “logs” that don’t have any practical impact I wonder if some other occurrences may generate problems in the future.

Aside from a few clients getting banned because of repeated occurrences of that error everything is working, it’s really a “better worry than sorry” thing. I noticed something strange to me and I want to double check now that I know I changed something rather than waiting for something to happen in a random future. :slight_smile: