Context deadline timeout error

[Akiranon]

Hello,

I've run into a somwhat strange problem. It seems that when I attach my certificate to more than 16 subdomains using Synoloogy's reverse proxy, I run into the following error:

2025/02/13 11:21:09 ERROR failed push to Synology error="push to synology for domain ***: execute request: Post "http://192.168.64.4:5000/webapi/entry.cgi?api=SYNO.Core.Certificate&version=1&method=import\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"

However, if I attach the certificate to 16 or less entries, there are no problems:

2025/02/13 11:25:44 INFO certificate uploaded certificate_id=***server_restarted=false

It seems that the more entries the certificate is attached to in Synology's reverse proxy, the longer it takes to replace it, and this seems to result in the above context deadline exceeded error.

Is it possible to increase the time limit of this action? Or perhaps make it user configurable?

[eherrm]

I get the exact same error, but in my case I get it even if I only have 2 entries in the built-in reverse proxy (under control panel - login portal - advanced - reverse proxy), but more than 11 services the certificate is assigned to under security settings (control panel - security - certificate - settings). I used the docker container to generate wildcard certificates for 2 domains, and I can assign up to 11 services to each/either domain without any errors, but as soon as I go past 11 on either domain I get the same error. It doesn't seem to be service related because I have all services assigned to one of the two wildcard certificates without error, and I also tried shuffling the certificates around between each service and the only common denominator for me seemed to be going past 11 services.