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
Hmmm, guessing the "expected to see" and "what did you see instead" sections are reversed, or are you reporting a previous problem has now gone away? 😄
Interesting. With your network connection, is it WiFi or cabled?
We've seen some weird behaviour before with WiFi connections, but we fixed "most" (!) of the problems. Most being "we thought we'd got it sorted, but turns out to be not 100%".
If this isn't a WiFi connection though, it'll be something else. 😦
64bit versions has trouble for me. DB Browser for SQLCipher.exe wants msvcr120.dll and not run. DB Browser for SQLite.exe open with error connection message.
Ahhh yeah. The current release doesn't yet support being used through a proxy. We added initial proxy support in the nightly builds a while back, if you're up for testing it? 😄
However, I have a home gateway from the ISP and an additional router connected to it. I'm using my own router for the WiFi, I don't know if it matters.
No worries. Probably the best move, though not fantastic, is to just turn off our automatic update check at startup. That should at least stop the error message from appearing.
At some point we'll probably need to write a simple utility specifically for testing why this is happening, or perhaps add some pretty extensive logging to the application.
It'll probably take a bunch of effort though, so unlikely to be in the near future. 😦
Happening for me too. I have never used this app before today. Win10 x64, v3.11.2. I am using WiFi. All browsers show the URL just fine. I am not using a proxy.
No Bob, I don't believe we know each other. I am simply using GitHub to reply to a thread about an open issue that is still occurring. You also replied to this thread (for the first time on Oct. 4, 2019). You can unsubscribe from the thread if you no longer want to receive emails about it.
As a general follow up with this, our recent 3.12.0-alpha1 release and the nightly builds from the last month or so onwards should be much better with this issue. They use a newer internal component (OpenSSL v1.1.1), which seems to be more reliable when making connections to our download server.
Activity
justinclift commentedon Jun 9, 2019
Hmmm, guessing the "expected to see" and "what did you see instead" sections are reversed, or are you reporting a previous problem has now gone away? 😄
justinclift commentedon Jun 10, 2019
@tgely ?
tgely commentedon Jun 12, 2019
I see the error message as reported in "expect" section on every program start. If I remember well 32bit version has no trouble.
justinclift commentedon Jun 12, 2019
Interesting. With your network connection, is it WiFi or cabled?
We've seen some weird behaviour before with WiFi connections, but we fixed "most" (!) of the problems. Most being "we thought we'd got it sorted, but turns out to be not 100%".
If this isn't a WiFi connection though, it'll be something else. 😦
tgely commentedon Jun 12, 2019
Its cabled. Probably should I install 32bit version instead? There was not error.
justinclift commentedon Jun 13, 2019
Yeah, definitely try that. 😄
chrisjlocke commentedon Jun 29, 2019
Any joy with the 32bitties version?
tgely commentedon Jun 30, 2019
64bit versions has trouble for me. DB Browser for SQLCipher.exe wants msvcr120.dll and not run. DB Browser for SQLite.exe open with error connection message.
32 bit versions work perfectly.
Eschato commentedon Jul 18, 2019
I have the same issue on WiFi with the 64 bit version.
Edit: and the 32 bit version as well.
justinclift commentedon Jul 19, 2019
Ahhh yeah. The current release doesn't yet support being used through a proxy. We added initial proxy support in the nightly builds a while back, if you're up for testing it? 😄
https://nightlies.sqlitebrowser.org/latest/
justinclift commentedon Jul 19, 2019
Oh... unless you're meaning that you're not behind a proxy at all?
Eschato commentedon Jul 19, 2019
Oh sorry, I meant I'm not behind a proxy at all.
However, I have a home gateway from the ISP and an additional router connected to it. I'm using my own router for the WiFi, I don't know if it matters.
justinclift commentedon Jul 19, 2019
No worries. Probably the best move, though not fantastic, is to just turn off our automatic update check at startup. That should at least stop the error message from appearing.
At some point we'll probably need to write a simple utility specifically for testing why this is happening, or perhaps add some pretty extensive logging to the application.
It'll probably take a bunch of effort though, so unlikely to be in the near future. 😦
35 remaining items
SoftwareTailor commentedon Oct 5, 2019
Yes. I'm using version 3.11.2. Qt version 5.7.1.
SoftwareTailor commentedon Oct 5, 2019
I found the Automatic updates option on the Preferences option of the Edit menu. I just unchecked it and the error message doesn't appear any more.
ronalddevos commentedon Nov 10, 2019
Same issue here, 3.11.2 with 5.7.1 - both on 32 and 64 bit version
mviens commentedon Feb 16, 2020
Happening for me too. I have never used this app before today. Win10 x64, v3.11.2. I am using WiFi. All browsers show the URL just fine. I am not using a proxy.
SoftwareTailor commentedon Feb 16, 2020
mviens commentedon Feb 16, 2020
No Bob, I don't believe we know each other. I am simply using GitHub to reply to a thread about an open issue that is still occurring. You also replied to this thread (for the first time on Oct. 4, 2019). You can unsubscribe from the thread if you no longer want to receive emails about it.
SoftwareTailor commentedon Feb 16, 2020
justinclift commentedon Feb 17, 2020
@mviens Does it still happen with our latest nightly build?
https://nightlies.sqlitebrowser.org/latest/
We're getting ready for a new release, and there have been a huge amount of code changes since 3.11.2, including some that may have fixed this. 😉
justinclift commentedon May 18, 2020
As a general follow up with this, our recent 3.12.0-alpha1 release and the nightly builds from the last month or so onwards should be much better with this issue. They use a newer internal component (OpenSSL v1.1.1), which seems to be more reliable when making connections to our download server.
SoftwareTailor commentedon May 18, 2020
MKleusberg commentedon Jun 3, 2020
@justinclift Do you reckon we can close this issue then? Or is there anything left we can do in our code to word around this issue?
SoftwareTailor commentedon Jun 3, 2020
justinclift commentedon Jun 4, 2020
Awesome. Done. 😄