- ago
0
1,055
Solved
16 Replies

Reply

Bookmark

Sort
- ago
#1
the ok button is grayed out for alpaca
0
- ago
#3
That's because WL8 is not CONNECTED to Alpaca. The OK button will only be enabled if Alpaca is connected.
0
- ago
#4
0
- ago
#5
I can get historic data using alpaca, but streaming failed
0
- ago
#6
I don't know really what to tell you besides try making a new Alpaca paper key. It's connecting at my end ...

0
Best Answer
- ago
#7


See this was the best place to ask this question again.

I got the "another connection might exist" issue. Btw I installed the Alplaca MCP server for Claude and added my PAPER keys on the 8th of May.

I uninstalled the MCP server, deleted my PAPER keys and made new API keys for a live account, but still no luck.



Looks like my Alpaca account is connected (greyed out).

Tried a full PC restart. Still no joy. Cant seem to get historical data since that night.

PS: I installed the MCP server on another machine.



Should i uninstall and reinstall WL8?
0
- ago
#8
I don't think uninstalling and reinstalling WL8 will help.

It looks like something else is connected to your Alpaca, we don't generate this message we're just the messenger in this case showing you what Alpaca is telling us.
0
- ago
#9
Thanks Glitch, however still experiencing problems getting Alpaca to stream after generating new API keys.

Isnt that the solution?
0
- ago
#10
Is it the same problem? Alpaca is reporting that something else is connected?
0
Cone8
- ago
#11
Only one connection instance with the Alpaca API is allowed. Is it possible that you're running more than one API connection - with WealthLab or any other client?
0
- ago
#12
I did try the Claude MCP that Alpaca developed but on another machine and then removed that connection.

Asked Alpaca if I can create a second account, but they dont allow that either.

Starting to run out of ideas hehe.
0
Cone8
- ago
#13
The message is that an existing connection still exists. If you don't think you have a client connected, get Alpaca to break whatever connection still exists. This is the problem.
0
- ago
#14
It seems somehow Claude/Alpaca is still holding that connection.
0
- ago
#15


The response from Alpaca.

But good suggestion from Cone, Il ask if they can break the connection.

Good point also from Glitch, but I removed the Alpaca connector from the JSON file in Claude.

Wondering if I should just create a new Wealthlab account. Alpaca only allows 1 account per person.
0
Cone8
- ago
#16
We don't limit the number of WealthLab connections to Alpaca, but we've observed that if you connect more than once, it's a problem - multiple instances won't get all the messages from Alpaca.

Here's the connect request and where the error is thrown due to the "Unauthorized" response. It's very clear that "not authorized" is coming from Alpaca.

CODE:
AuthStatus status = _dataStreamingClient.ConnectAndAuthenticateAsync().Result; if (status != AuthStatus.Authorized) throw new RequestValidationException("Unauthorized status returned for data streaming client. Another connection may exist.");


1

Reply

Bookmark

Sort