On your microSD card, there will be a root or log folder with the device log that you can access with a computer. The files are named as xxxxx_log.txt. If there are multiple logs, select the most recent log file.
Just bought three cameras and all were working fine until I updated them. At first I only updated 1 camera and noticed the failure to connect error 13 messages right away. The other two cameras were still working perfectly. Then I updated the remaining two cameras and immediately got the error message on all three cameras. Clearly the latest update is buggy. WYZE needs to correct this issue asap.
Adding the following data point, when exclusively on mobile data connection I can reliably run a command like the next, but as soon as wifi (over home router) comes into play, I get the ssl errors again:
Maybe a better solution than the environment variable: On my Arch Linux machine with nix installed it was enough to start my systemd-timesyncd.service that was not started for some reason anyway to make the errors disappear.
I'm using the Download tool to post my API and send some data as the last step of my workflow, but i'm getting the error "Error transfering data: SSL connect error" on the tool and I can't figure out as to why.
I recommend a chat with your IT folks on this. I had a similar experience trying to hit an API and the IT team found that some of the calls were getting dropped because of the way the outbound traffic was being handled.
Hello @JonathanAllenby seems I am getting similar Error, the thing is that in my Local I do not see any issue running the Macro basically I am extracting Data from our Survey system tool via an API but when I use the Jump server to run it I get the Error (I have to use a jump server because I have to write to a SQL table and my local do not have the permission to do so), so my question is if you have any specific info on what needs to be adjusted to resolve the SSL Error, below is high level overview of the Macro, basically Error occurs in the download tool:
Hey @shevshenko - I'm afraid I don't I spent a long time researching this myself through various community posts and internet resources before the user I was working with resolved it with the information in my last post being the extent of the detail they offered. All I can provide myself information-wise is the summary I sent to them before they located their specific issue:
The only option we have available is to request that your IT department investigate first as usually the cause is found through an internal investigation into the certificates and proxy settings.
Following that investigation all we can do is contact Alteryx Support.
Here are two of the community articles with actual advice on the subject which may help guide your IT team:
I built a workbook around the StockHistory function to track the stocks in the S&P 500. I did this a few months ago and I update it once a day. Each stock is presented according to which SPDR Sector the stock resides in. The workbook keeps track of various moving averages, gives me the percentage of stocks by market cap below those various averages. It also computes relative strength for each stock as it compares to the SPDR Sector it is in. Frankly the StockHistory function has been tough to work with and requires a lot of TLC. Refinitiv's data can be pretty hit or miss. A number of the tickers are missing data for a day in the past year or so. It requires a workaround.... no big deal but you would think they would clean the data they distribute so it is correct.
This week I have come across a new error and that is StockHistory returning a #Connect! error. I have spent way too much time looking on the Internet for what is happening and there are only a few posts on various boards that even mention this. One post says that it means the server is busy and try again later. I have done that and it still doesn't work after multiple tries.
To be clear, there have been no changes to my spreadsheet and this error just started appearing. I would have thought that if Microsoft has Excel return an error they would have an easy to find explanation of the error and steps to correct it but if it is out there I can't find it.
@djgabel Hi, I am doing something broadly similar, and also find STOCKHISTORY (,...) to be very hit or miss. I can enter XLON:AAL for example in a row of other stock tickers, and the function throws up an error such as #VALUE, or #CONNECT. Exactly the same formula pasted into a cell elsewhere on the same, or a different sheet, produces the expected column of dates and closing prices. My searches have so far failed to find explanations of the error messages. This is all very frustrating, as I am writing VBA macros to model efficient portfolios, and do not have the funds to buy all this data separately. The model will fail on a GIGO basis with ill-conditioned data inputs.
@John_Weaver Without examples it is tough for me to say what is happening. I use stock history on roughly 500 stocks (S & P 500) and each stock gets its own column which at the top has its own STOCKHISTORY formula typed in. Since these are large and well known companies I never type the exchange to use in the formula, it just figures it out and displays that in the header along with the ticker. The #Connect! error happens ocassionaly and in my experience is an issue between MSFT and Refinitive their data supplier. Waiting an hour or so always seems to fix that issue but if it doesn't on occasion just deleting the entire column and retyping the formula clears it up for me. That does not happen a lot but when it does I know it is frustrating.
Yes indeed. Imagine a row of Stock fields already showing the correct company names linked to the market code ("Ticker" in the UK). Then in the first cell under these headers is the filled out STOCKHISTORY function, resulting in two columns underneath containing the hoped-for dates and associated closing prices. I am at the stage of building up a database of the FTSE100 companies, going back to 1988, so many gaps, companies come and go, new ones arrive etc. So fragmentation is to be expected. That successful formula in the first cell has been copied and pasted across the row directly under the headers, and that is where the trouble starts. Most columns quickly light up with the desired info, but some do not. It implies quite a bit of oversight and manual data cleaning on my part before I can trust it enough to feed into my model.
@djgabel I think they have a lot of problem in terms of data accuracy. I tried to use it to track the historical price of vbal, which is a Canadian stock. But the closing price is wrong from the beginning. it is usually about $.20 above the actual price. They only provide correct price beginning from January 2023.
Similar to the familiar "404 Not Found" and "500 Internal Server Error" statuscodes you may have seen in HTTP, Connect uses a set of 16 error codes.In the Connect protocol, an error is always represented as JSON, and is easilyreadable in the developer tools of your browser. For example:
The code property holds one of Connect's error codes.All error codes are available through the TypeScript enumeration Code.Note that a code is an integer value, but can easily be converted to andfrom a string value.
The message property contains a descriptive error message. In most cases,the message is provided by the backend implementing the service. Becausemessage is the only property that shows up in the browser console foruncaught errors, the error message is always prefixed with the error code.In case you do want the original error message without a code prefix, usethe property rawMessage.
If you catch an error, your program takes an exception from the regular codepath, but you might still want to access a header or trailer value. Connectprovides a union of header and trailer values in the metadata property as asimple Headers object:
On the wire, error details are wrapped with google.protobuf.Any, so that aserver or middleware can attach arbitrary data to an error. Using the methodfindDetails(), you can decode the details from an error.
Yes, neither of those fix this error. For some reason the work around is to go to Actions Invoice Transfer Invoice and create a new group name. Then it allows us to print the edit list and post. It happens very randomly, but is becoming frustrating for our AR admin.
After a closer look today it seems like the validation is looking at all invoices using the same GroupID, even the ones already posted, and if they are marked for tax connect calculation and the status found is not correct it is triggering the error. Which is why using a unique never used before GroupID fixes it.
In theory, if an invoice was processed through tax connect and posted successfully in the ERP, it should have the correct status and the error should not happen, but it seems like it can happen and here we are.
Hello. First time poster here!
I would like to ask if anyone has any recommendations for safely removing all remnants of a Juniper Secure Connect Client.
I am trying to install a client build of 48591 on a Windows 10 OS but receiving a 1722 error at what looks to be during the network adapter initialization. I am able to install this fine on a clean PC but any PC that has had a previous version of build 29669 will fail with the error stated above.
I know the 1722 is a pretty generic error and I have attempted what feels like anything and everything recommended online. This includes cleaning registries, program files, drivers etc. but I am not able to resolve this problem.
Just wondering if anyone has any suggestions or a clean install procedure for such a situation?