Jump to content
TorGuard
  • 0

TorGuard Client v4.7.0 (BETA)

Rate this question


Support
 Share

Question

==================================
The following is a BETA release for TorGuard
Release torguard-v4.7.0 2021-05-07
===================================
- All platforms: ShadowSocks is now enabled on most locations.
- A new option "ShadowSocks enabled" is visible on the Connect screen when OpenVPN and TCP protocol are selected
- Linux: fix "Auto start on boot"

 

Downloads

  • Thanks 1
Link to comment
Share on other sites

4 answers to this question

Recommended Posts

  • 0

On ubuntu 20.04 no issues during installation (however, it shows v4.6.2 despite me clicking on downloads "BETA", ), connecting to first (default) server which is USA-Dallas

default-server-fails-on-handshake.png

After first launch, trying to connect results in a handshake error, closing the TorGuard client and restarting it resolves this known issue.

Connecting (it takes few seconds until verified is shown), default protocol: wireguard: 

image.pngimage.png

image.pngimage.png

 

That would be it, for now, everything else works as expected (except maybe that known bug with first time start and requirement to shutdown a client, maybe a popup notifying user about it would do the trick too. I have no issues at all for now with this beta client.

Here are screenshots default properties (installed on a clean ubuntu):

image.pngimage.png

image.pngimage.png

image.pngimage.png

image.png

  • Thanks 1
Link to comment
Share on other sites

  • 0
16 minutes ago, 19807409 said:

it shows v4.6.2 despite me clicking on downloads "BETA",

Is this now 4.7 beta where version was not updated or is it v4.6.2? Hashes are clearly different:

torguard-latest-amd64.deb - Link for latest client (I suppose it is 4.6.2)

torguard-latest-amd64 (1).deb - Supposed beta client showing v4.6.2

sha256sum torguard-latest-amd64*
025759b98ee15d90e103a49d71e7d9b5b796838d0b4fb02bdc7f7f79020d3cbb  torguard-latest-amd64 (1).deb
984dcf4c87c1ca0e87c5181e472021e45f9f7aec2a97ed825443116641c96aa8  torguard-latest-amd64.deb
md5sum torguard-latest-amd64*
12436d7704d2c2cc37fc51a14ac7a476  torguard-latest-amd64 (1).deb
68551fb20b234b01755d4e6d7ad074a6  torguard-latest-amd64.deb
sha1sum torguard-latest-amd64*
07e1b95d01c7df06527af082e231f9dd7f91bee9  torguard-latest-amd64 (1).deb
a123a5ae0937ab81906d0682328f014a4d0f11eb  torguard-latest-amd64.deb

@Support which version is it then?

BTW: here is help for torguad bin:

TorGuard command line.

Options:
  -h, --help                                           Displays this help.
  --library-test                                       Try to run TorGuard in
                                                       order to check that all
                                                       libraries are installed
                                                       in the machine.
  --cleanup                                            Clean up after
                                                       application was force
                                                       fully quit or sig term
                                                       was received.
  --settings <rewrite|reset>                           - rewrite: load, delete
                                                       and rewrite the
                                                       configuration file. It
                                                       can solve some permission
                                                       problems.
                                                       - reset: reset the
                                                       settings to default.
  --service-address <address>                          Address where the
                                                       service runs (must be
                                                       used together with
                                                       service-port).
  --service-port <port>                                Port where the service
                                                       is listening (must be
                                                       used together with
                                                       service-address).
  --enable-qml                                         Enable Qml Window.
  --disable-qml                                        Disable Qml Window.
  --showTheme <themeValue>                             Show GUI theme
  --enableAccessibility                                enable Accessibility
  --disableAccessibility                               disable Accessibility
  --guiSettingsUtility <disableOpenGL | enableOpenGL>  disableOpenGL: disable
                                                       OpenGL
                                                       enableOpenGL: enable
                                                       OpenGL

  --beta-multi-windows                                 Enable multi window
                                                       functionality.
  --record-session <file>                              Record messages sent
                                                       from backend to frontend
                                                       in a file
  --enable-websocket <webSocketPort>                   Use WebSocket
                                                       communication. This
                                                       option must be an
                                                       available port number.

 

but there is no --version option to show binary build/version info, maybe you should add it to prevent such confusion.

Link to comment
Share on other sites

  • 0

Thanks for checking this out - the beta is indeed v4.6.2 (should be 4.7.0) my bad but still has the new changes listed  - in regards to the Wireguard issue, did this happen before for you or just on this build?

Thanks again 👍

Link to comment
Share on other sites

  • 0
2 hours ago, Support said:

Thanks for checking this out - the beta is indeed v4.6.2 (should be 4.7.0) my bad but still has the new changes listed  - in regards to the Wireguard issue, did this happen before for you or just on this build?

Thanks again 👍

You are welcome, I was just confused by different file hashes and versioning but assumed it is correct one where simply the version was not bumped, thanks for clarification.

In regards of the error, this happened already with old beta and is actually known issue where from time to time somebody posts question about. I did debug this some time ago, its nothing cruical, just wanted to let you know that this happens on first launch of the app if there is no userdata available (like fresh install), then user is asked for credentials and then handshake fails, simply shutting the client down and starting it again resolves this issue which only happens once until is resolved and does not come back again (unless one uninstalls fully and reinstalls). It is reproduceable.

  • Thanks 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...