You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I created a sever on GCP and I tunnel it to my local computer via putty.
As you can see in the server log, the codex plugin you made is not talking to the right server. I am confused if it is security issue on the GCP side, or the tunnel, or if your code dont allow this possibility.
----this is interesting because its an cloud application, so far it works fine locally----
this is my server log: [I 2021-09-22 19:00:03.921 ServerApp] 302 GET / (::1) 0.61ms [W 2021-09-22 19:00:07.030 LabApp] Could not determine jupyterlab build status without nodejs [W 2021-09-22 19:00:08.247 ServerApp] Notebook Untitled2.ipynb is not trusted [I 2021-09-22 19:00:08.739 ServerApp] Kernel started: c9114e1c-70b4-4791-b32d-35aae6dbc686 [W 2021-09-22 19:00:12.470 ServerApp] 404 POST /jupyterlab-codex/completion?1632337212823 (::1) 26.81ms referer=http://localhost:8888/lab/tree/Untitled2.ipynb
The text was updated successfully, but these errors were encountered:
I created a sever on GCP and I tunnel it to my local computer via putty.
As you can see in the server log, the codex plugin you made is not talking to the right server. I am confused if it is security issue on the GCP side, or the tunnel, or if your code dont allow this possibility.
----this is interesting because its an cloud application, so far it works fine locally----
this is my server log:
[I 2021-09-22 19:00:03.921 ServerApp] 302 GET / (::1) 0.61ms [W 2021-09-22 19:00:07.030 LabApp] Could not determine jupyterlab build status without nodejs [W 2021-09-22 19:00:08.247 ServerApp] Notebook Untitled2.ipynb is not trusted [I 2021-09-22 19:00:08.739 ServerApp] Kernel started: c9114e1c-70b4-4791-b32d-35aae6dbc686 [W 2021-09-22 19:00:12.470 ServerApp] 404 POST /jupyterlab-codex/completion?1632337212823 (::1) 26.81ms referer=http://localhost:8888/lab/tree/Untitled2.ipynb
The text was updated successfully, but these errors were encountered: