-
Notifications
You must be signed in to change notification settings - Fork 500
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TabNine::config page always be blank on vscode-remote #305
Comments
Hey @FourLeafTec I'm sorry you encounter such problems. Lets try to resolve that issue for you! Could you press Thank! |
Thanks for the response @FourLeafTec Actually I'd need you to open Tabnine Hub using in the browser (type Thanks, and sorry for being unclear. |
I have the same problem and can't open a browser either. Just did a fresh reinstall too |
I have the same with tabnine pro. On a local vscode it works fine, but running with WSL - the config page stays blank. tabnine::config opens a page on localhost - http://127.0.0.1:5555/nomomtejndmazgriqjau But when running with WSL, that does not lead to the config page. The problem seems to be that the tabnine host runs within WSL, and listens on 0.0.0.0 and only accepts localhost connections. (From the WIndows 10 host into WSL is technically not a localhost connection, as WSL2 has it's own network and IP address) What works, is running a SSH tunnel - ssh -L 5555:127.0.0.1:5555 username@[wsl ip address] And then connecting to localhost:5555/[config-url] But this is quite bothersome and it used to work just fine a few months ago. |
Any update on this? This is quite the problem and I at least expect an acknowledgement of the problem after paying for the product. (Call me spoiled or whatever.....) ;) |
Experiencing same issue when using Remote-SSH with a mac host. VSCode 1.55.0-insider |
Also having the same issue, can't add the API key and I'm running into the daily limit for free fairly quickly. Found the way to do it manually though: In your terminal whilst in your homefolder: Now you can open that file and add the api_key. After you've added the api key it will take a little while for it to load that or you can just restart vscode. Now I have tabnine pro running on my local ubuntu vm w/o using the tabnine hub page. |
The issue is that the port 5555 does not get forwarded by default. If using remote SSH vscode extension please add port 5555 to your config. Fro the development team of this plugin, I think you should be able to set this option programmatically during setup. |
@sanderkooger Thank you so much for the solution! :D Everything is working great now. :D |
@MrQrax I was hopeful that @sanderkooger 's solution would work for me but I set up port forwarding on 5555:5555 but I still get nothing in the browser or on TabNine Hub in vscode. It shows up as normal when I am in a local workspace. Any idea what I might be missing? |
Any updates?? |
Same issue. Because of this issue, I cannot enter the API key to upgrade to Tabnine Pro after purchasing it, which is frustrating. |
Same here!! |
if u having this issue (USING REMOTE SSH) |
Doesn't help under the VPN connection. (That allows ports, incl. 5555
passthrough).
…On Wed, Apr 28, 2021 at 9:24 PM IvsonSilva ***@***.***> wrote:
if u having this issue (USING REMOTE SSH)
Press F1 > Forward a Port > Add port this port> 5555 > Save > Now u can
open tabnine Hub :).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#305 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABW2N7WTCLR34FYDICPHPTTLDNPPANCNFSM4UJ74JEQ>
.
--
Mikhail Yurasov
|
This does not work for me |
Do this when u connected to the remote ssh, if this doest work, try to
check if u computer are blocking local ports or if the port 555 has aready
in use
Em qui, 29 de abr de 2021 09:09, Jack Rory Staunton <
***@***.***> escreveu:
… if u having this issue (USING REMOTE SSH)
Press F1 > Forward a Port > Add port this port> 5555 > Save > Now u can
open tabnine Hub :).
This does *not* work for me
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#305 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATCRZ6NNSS7TBECC4N7ARGTTLFEARANCNFSM4UJ74JEQ>
.
|
It Resolved For Me. |
my blank tabnine hub was fixed by |
I had the same issue with wsl 2 [Debian]. But this worked for me: Just drag and drop the sign-in/sign-up button in the TabNine hub page in your browser. |
How do you get the API Key? I can't see anything for it in the tabnine site. |
I'm using code-server and it's also broken for me due to TabNine trying to connect to 127.0.0.1 instead of the FQDN that vscode requires. I couldn't find a setting for TabNine that even allowed this to be changed. |
I have the same issue |
For now I've worked this around with connecting to the server where my code-server is with ssh and port forwarding: ssh -L 5555:localhost:5555 code-server.mydomain.com |
I'll put the solution that worked for me first: The symptoms for me was that even with SSH port forwarding, I would see the page render for half a second, then go blank.
and
|
I’m having the same issue with TabNine config hub on a remote VSCode setup. I’ve port forwarded 5555 to the remorse server where TabNine is running, but still no luck. How do I figure out what the random string is to access http://127.0.0.1:5555/{what-do-i-put-here} ??? |
@ksylvan - I'm guessing that 'if' the tabnine binary is running on the remote linux server, and you have 'triggered' the tabnine openHub command. You could login to the remote host in a different terminal window and try something like |
Hmmm… After port forwarding 5555, I see the same symptoms as @camAtGitHub when trying http://localhost:5555; namely, I see the page render for a fraction of a second, then a blank page. Using Web Inspector, I see these errors:
My TabNine version is 3.6.14 Help->About on VSCode shows this:
|
When visiting http://localhost:5555/preferences I see these errors in JavaScript console:
|
@ksylvan my previous post was to help try identify the secret/magic string.
also it may help if lynx is also installed on the remote server when you
attempt this. give it a try.
|
@camAtGitHub - I see. I don’t use nvim and I am seeing what you stated earlier, which is that the TabNine config page seems to pop up for a second and then becomes a blank page. And I see the above JavaScript errors (as others have seen in this thread) |
@ksylvan - I know that your using vscode... I didnt say anything neovim specific.... And no I'm not prepared to help you set it up. Anyway I have tested the below on vscode w remote workspace. Try the below:
Good luck & Turning off notifications, |
Thanks, @camAtGitHub - That pointed me to the magic. With the “Error Lens” extension installed, I typed: // tabnine::config And then the following was highlighted with a Tab to insert showing:
So I hit Tab and now was able to put my cursor on the link and Follow Link… But it still does not work to render the page. |
Looks like the tabnine web code should be changed to use something like {baseURL}/proxy/5555 instead of 127.0.0.1:5555 for the hub page, since this PR went into the base code-server: coder/code-server#5624 @jsjoeio |
Any updates on this? |
Still waiting to hear back from tabnine team |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
any news? |
any news regarding this? |
This is not stale, I just ran in to this same issue. Had to use DevTools to exract the link in order to login See #377 |
any news regarding this? Has anyone had a solution to this problem? |
TabNine::config page always be blank on vscode-remote
And I can't find useful log.
The text was updated successfully, but these errors were encountered: