Reverse proxy for Synology NAS

[SimonDPro]

Hiii, first of all, thanks for this amazing application. I have started to use it few days/weeks ago, and i really like it.
But i have some problems for the reverse proxy.
My first openem server attempt was in a Linux server : and it worked perfectly.

But now i want to use it on Synology NAS, with docker... It work without proxy, but when i want to try with proxy, ihv no idea how to do it.
I tried many things, Caddy : but it didn't work, I tried the Synology NAS native reverse proxy, but it didn't work with Let' Encrypt... And i even tried to change nginx.conf file on the NAS, but when i restart, it wipe all my changes.

Any idea ?

[doncicuto]

Hi @SimonDPro , thank you for opening this issue and for giving OpenUEM a try

I have no previous knowledge about Sinology reverse proxy and while the reverse proxy configuration can be tricky I hope we will make it work.

First of all. If you want to use the console behind the reverse proxy and use lets encrypt the authentication with client certificate wont be available, only user/password and/or OpenID Connect will work.

As you will use Docker one of the things you will need is to let the console know which is the domain name and port will be used for the reverse proxy. You'll need to set REVERSE_PROXY_HOST and REVERSE_PROXY_CONSOLE_PORT env variables.

For example if you want to use console.example.com and port 443 to reach the console you will set those variables and configure your reverse proxy accordingly

You may have already tried these suggestions so let me know what you tried and provide your .env file for OpenUEM and reverse proxy settings to check together what may be wrong

Thank you!

[doncicuto]

Morning!
Thank you for your answer, I'll use it to improve the docs about reverse proxy and Sinology. Glas that you can work using plain user/pass auth.

About the second part, the office365 issue... Is the console preventing you to select the SMTP auth type in the SMTP tab or is it something in office365 that dislikes LetsEncrypt certificates, I've followed my code for both the console and the notification worker and can't find the issue to find a workaround (I don't have Office365 to test anyway...)

[SimonDPro]

Hii,

You'll see what I did on the screen. I just removed the e-mail adress for both : user and Mail From, for the screenshot.
And it gives me the error message : SMTP AUTH failed: 535 5.7.3 Authentication unsuccessful.
But the password is 100% correct.

It doesn't give me the option to select "STARTTLS or SSL/TLS", like usual interface.

And last thing, when i reload the page, it automatically changes "XOAUTH2" to "LOGIN"

[SimonDPro]

0 emergency, for the moment I can still use ssl0.ovh.net server. But I would like to use office365 instead.

Thanks for all you answers, you'r great

[doncicuto]

Ah yes I see, the refresh issue is a bug form the interface that I must fix

For the Office365 mail service to work, I read somewhere that xoauth2 was the preferred way and that the user/pass method was going to be deprecated but I'm not sure. Wish I had an account to test it as it should be indeed a common use case to have this server to send email notifications.

If you can think on a way I can test this (development account or something) it would be great (I don't want to pay one month of service to Microsoft 😂)

Thank you for raising these issues it helps me a lot to improve the support

[SimonDPro]

Thanks
Yes it will be xoauth2 100% in few years

Yeah I understand 😄
I'll see what I can do for you, but not 100% sure of the result... I'll let you know

Thank's to you

[SimonDPro]

Little update :
Hiii,
Sorry but the internal policy doesn't allow me to give licences for external peoples...

Thnks a lot for your answers btw