AlBundy33

what do you think about an environment-variable DISABLE_OOB that is automatically added to sqlnet.ora on first start?

using a setup-script seems to work but requires an additional folder an file this and my workaround ``` # executed after container is started and prepared docker exec oracle1 "/bin/sh"...

Of course it os a server-side param - I set it currently only on the server because the are multiple clients (jdbc, odbc, crystal reports, ...)

for jdbc I do not have to install oracle instant client and I currently set DISABLE_OOB only in the server container and leave the clients untouched. I was pretty sure...

No - because I didn't want to change all client-settings. Therefore I've added DISABLE_OOB=ON to sqlnet.ora on the server-side which works as expected for java applications as well as for...

But there seems something wrong if the incoming calls are not assigned to the correct account. 🤔 At least a workaround to disable the filter in the proxy-accounts would be...

switching from #831 Due to your comments I've checked my proxy-settings where something like this was set: ``` sip-address: "Al" sip-server-adress: ``` Now I've changed the sip-address to `sip-address: "Al"...

Then you have hopefully a backup of the file or printed it out. Without the keyfile there is no chance to open the database. you can also have a look...

Maybe this is more an issue with pCloud. Keeweb did not work out of the box with my synology nas but after some changes in the webserver config. see #314...

the site uses lets enceypt and has currently a valid certificate.