Closed masatatsu8 closed 1 year ago
The environment variables http_proxy and https_proxy are configured in Windows system preferences and .env.local.
@masatatsu8 are you still having this issue? what is the callback url on the GitHub OAuth apps?
@thivy Yes, I still have the issue. The call back url is the following one as described in README. It worked fine on another PC.
we use a proxy as well in our environment and is very painful.
We had to patch the next-auth files in order to make the login work. This seems to be the desired behaviour (for whatever strange reasons), see https://next-auth.js.org/tutorials/corporate-proxy The patch files in the docs are no longer up-to-date. Better edit the files in the node_modules folder manually and create a patch out of it for automation
After being able to login behind a corporate proxy we still struggle with the call to the Azure OpenAI instance using a proxy. This seems to be done using the axios framework. So far I was not able to pass the proxy
, https-agent
or whatever in a way that works.
Unfortunately setting http(s)_proxy
(alone) does not work. Each http client used in the application seems to expect a different proxy configuration.
I successfully got the app to work on a local machine directly connected to the Internet, using GitHub authentication.
Next, I tried to get the app to work on a PC connected to the company network under proxy management, using the same API and authentication settings.
But I got the following error and GitHub authentication failed.