[Bug]: Failed parsing configuration: Error while parsing time

[roman80k]

Before submitting, please confirm

• I read the README and followed all setup steps in order
• I searched existing issues and found no duplicates
• I am using the latest version of the TrustTunnel console client

Environment details

• OS: Windows 11
• Architecture: x64

App version

1.0.31

Steps to reproduce

1. Run wizard
2. Follow wizard
3. Edit generated config, because somehow it does not contain endpoint address (as server/endpoint config file too)
4. Run client
5. Get the error: ERROR [15628] TRUSTTUNNEL_CLIENT_APP main: Failed parsing configuration: Error while parsing time: expected ':', saw '7'

Expected behavior

Working tunnel

Actual behavior

Error related to parsing time

Screenshots

Screenshot 1

Additional Information

No response

[anyakushin]

@roman80k Hello! There is definitely a TOML syntax error that was made during editing the config file. Make sure that all strings are put inside double quotes ". You could check the example configuration to see how the syntax should look like.

Also the wizard is always asking about the endpoint address and injects it in the generated config file so i doubt why it is not suitable for you. If you are using the export config function from endpoint, then you have to specify the ip address during exporting via --address argument because endpoint is unaware of the public ip address that is used to access it.

[roman80k]

Thanks for fast reply. I have adjusted example config and got further, but now it fails with error mentioned here:

#28

"Failed to ping location"

[anyakushin]

Hi, @roman80k , sorry for a long reply.
Have you figured out your issues?
I recommend double check the config values, especially endpoint related fields. The Failed to ping location is either the wrong endpoint settings or very drastic DPI blocking.
You could also enable the debug logging (loglevel = "debug" in config), might it help to investigate what is going on

[roman80k]

Hi, @roman80k , sorry for a long reply. Have you figured out your issues? I recommend double check the config values, especially endpoint related fields. The Failed to ping location is either the wrong endpoint settings or very drastic DPI blocking. You could also enable the debug logging (loglevel = "debug" in config), might it help to investigate what is going on

Hey Andrei,

No I haven't, I've found another solution for my needs. But you might be right, this could have been due to DPI: I was performing this on cellular/mobile internet.

[anyakushin]

Thanks for you reply!

I am closing this for now still the originally stated issue was solved.

If there will be any progress according to the Failed to ping location error, it will be discussed in #28