Open VictorHachard opened 3 months ago
Thanks, the double /
is the issue
Probably something as easy as changing the following code block:
const { server } = await this.configCore.getConfig();
const baseUrl = () => {
let url = 'http://localhost:2283';
try {
var url = (new URL(server.externalDomain)).origin;
} catch (e) {}
return url;
}
const { html, text } = this.notificationRepository.renderEmail({
template: EmailTemplate.WELCOME,
data: {
baseUrl: url,
displayName: user.name,
username: user.email,
password: tempPassword,
},
});
(if you don't care about IE you can remove the (e)
part).
Ideally this should be earlier on, especially if server.externalDomain is used elsewhere, but this should work.
Let's instead normalize it in getConfig instead.
For the styling issue, I transferred my email to Outlook, and there is no problem. It seems to be an issue with Gmail.
INFO: not fixed in v1.107.2
The bug
I have configured a mail server with Google. However, I have two issues:
I see in the code that the base URL is concatenated with
/auth/login
. In my case, the base URLhttps://xxx/
combined with/auth/login
results in the double slashes (https://xxx//auth/login
).Also, I am using Nginx with Nginx Proxy Manager. Could this be causing the ending / in my base URL?
The OS that Immich Server is running on
TrueNAS-SCALE-23.10.2
Version of Immich Server
v1.105.1
Version of Immich Mobile App
v1.105.1
Platform with the issue
Your docker-compose.yml content
Your .env content
Reproduction steps
Relevant log output
No response
Additional information
No response