The only way to turn that setting back off is via a database edit as mentioned here:
If this is with Docker, then to run the command you would need to do the following:
To fix the underlying issue, assuming the CMS is behind an Apache reverse proxy, you would need to add the following to the Apache configuration:
proxy_set_header X-Forwarded-Proto $scheme;