Google sign-in blocks an internal Outline Docs setup
A workplace-only is being set up with . The app is already running in a , and the same tool works at home through authenik on a personal domain. At work, the goal is to let staff sign in with their accounts.
The setup gets difficult because Google expects a full web domain, while the service only has an internal address and port. Using nip.io makes the internal address look more like a domain, and that partly works. The next blocker is that sign-in requires HTTPS instead of plain HTTP.
A self-signed was added by following guidance, but after that the page stopped loading. The practical problem is making , a domain-like address, and HTTPS work for a service that is not exposed to the public internet.
Key points
- is being used as an internal option.
- The is already running successfully.
- sign-in does not fit neatly with a bare internal address and port.
- nip.io can make an internal address look like a domain, but it does not solve every issue.
- HTTPS and the self-signed step caused the service to stop loading.