Ask a Question
GoPro Support Hub Ask a question. Share an answer. Find a solution. Stay stoked.
Announcements
Is your GoPro gear up to date? Check to see If it is on our Update page.
GoPro Apps for Desktop
Reply
Sightseer
Posts: 1

Re: Can`t login, still "Authenticating..:" without effect

[ New ]

I can confirm after hours of messing around with this on my new 2018 MBP, the post @dominicm3586 posted works. Go to the link here: follow their steps using X-Edit and follow the post writing the code into you hosts file. Mine was greyed out... Couldn't drag over to the desktop to edit and this was my only option. Saved what I wrote in the file (which was originally empty, no text) and re-opened the app. Everything is now working!!!

 

https://www.imore.com/how-edit-your-macs-hosts-file-and-why-you-would-want

 

Good luck!

Sightseer
Posts: 1

Re: Can`t login, still "Authenticating..:" without effect

[ New ]

I have confirmed that the solution provided by @connyf668:

 

"Move the 127.0.0.1 localhost entry to the very top of [your /etc/hosts] file."

 

is the right solution!!!

 

Thank you @connyf668 for figuring that out. Smiley Happy This has been the most perplexing problem I've ever encountered with a piece of software; and is a sad testament to GoPro's ability to support their software. I primarily use this app for syncing the clock and for the occassional firmware update of my GoPro. It's also handy for copying files off without having to extract the tiny SDCard from the GoPro.

 

I dislike using the iOS and Android app because it just doesn't work well. Getting the wifi connection to work is so fraught with problems I just finally gave up. 

 

Thank you again, @connyf668 for clarifying the real solution to the problem, you made my day, my week and my month!

Sightseer
Posts: 3

Re: Can`t login, still "Authenticating..:" without effect

[ New ]

Moving localhost to first line didn't solve the login issue. Useless piece of software! We can't even login.

@jefft Can you please help?

Sightseer
Posts: 3

Re: Can`t login, still "Authenticating..:" without effect

[ New ]
Sightseer
Posts: 1

Re: Can`t login, still "Authenticating..:" without effect

[ New ]

Yes I had the same issue took me 2 hours to figure out. 

Finally got it. 

 

Step by step to fix the issue of getting stuck with the Authenticating message: 

Step 1: right Click on finder and click "go to folder"

Step 2: copy paste /private/etc/hosts and click "go"

Step 3: copy "hosts" folder to your deskop

Step 4: Open the folder and Delete all the content in the "hosts" file and past the below: 

##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
fe80::1%lo0 localhost

Step 5: Safe the folder and copy it Back to the orginal place: /private/etc/hosts and click "Replace"

Step 6: reopen Quick it will work

Sightseer
Posts: 1

Re: Can`t login, still "Authenticating..:" without effect

[ New ]

I wasnt able to copy the document, so i just opend txteditor, copy pasted the content over then replaced this file with the hosts file. Works now.

Sightseer
Posts: 1

Re: Can`t login, still "Authenticating..:" without effect

[ New ]

hi, 

I faced an issue that after login, I want to go "creat mode" then it goes back to the login page again...

I checked on this, lots of users faced the same problem as me, please provide the solution. 

Hiker
Posts: 10

Re: Can`t login, still "Authenticating..:" without effect

[ New ]

Thanks bro..is working now with your detail steps provided..

Sightseer
Posts: 1

Re: Can`t login, still "Authenticating..:" without effect

[ New ]

have same issue mac os 10.14.3

host file doesn't help

 

console output:

 

error 10:11:01.732511 +0800 GoPro Quik TIC Read Status [1:0x6000010bdf80]: 1:57
default 10:11:01.732550 +0800 GoPro Quik TIC TCP Conn Event [1:0x6000010bdf80]: 2
error 10:11:01.732569 +0800 GoPro Quik TIC Read Status [1:0x6000010bdf80]: 1:57
error 10:11:01.732582 +0800 GoPro Quik TIC Read Status [1:0x6000010bdf80]: 1:57
default 10:11:01.732630 +0800 GoPro Quik TIC TCP Conn Cancel [1:0x6000010bdf80]
default 10:11:01.732674 +0800 GoPro Quik [C1 Hostname#09b7f53c:443 tcp, url: https://api.gopro.com/v1/locations/geoip.json, tls] cancel
default 10:11:01.732762 +0800 GoPro Quik [C1 Hostname#09b7f53c:443 tcp, url: https://api.gopro.com/v1/locations/geoip.json, tls] cancelled
[C1.1 <private> 192.168.1.6:49983<->IPv4#4fd94374:443]
Connected Path: satisfied (Path is satisfied), interface: en0, ipv4, ipv6, dns
Duration: 62.170s, DNS @0.000s took 0.003s, TCP @0.005s took 0.185s, TLS took 0.319s
bytes in/out: 6075/652, packets in/out: 14/7, rtt: 0.115s, retransmitted packets: 0, out-of-order packets: 0
default 10:11:01.732784 +0800 GoPro Quik 0.000s [C1 <private> Hostname#09b7f53c:443 resolver] path:start
default 10:11:01.732810 +0800 GoPro Quik 0.000s [C1 <private> Hostname#09b7f53c:443 resolver] path:satisfied
default 10:11:01.732826 +0800 GoPro Quik 0.000s [C1 <private> Hostname#09b7f53c:443 resolver] resolver:start_dns
default 10:11:01.732842 +0800 GoPro Quik 0.003s [C1 <private> Hostname#09b7f53c:443 resolver] resolver:receive_dns
default 10:11:01.732931 +0800 GoPro Quik 0.003s [C1.1 <private> 192.168.1.6:49983<->IPv4#4fd94374:443 socket-flow] path:start
default 10:11:01.732987 +0800 GoPro Quik 0.003s [C1.1 <private> 192.168.1.6:49983<->IPv4#4fd94374:443 socket-flow] path:satisfied
default 10:11:01.733077 +0800 GoPro Quik 0.005s [C1.1 <private> 192.168.1.6:49983<->IPv4#4fd94374:443 socket-flow] flow:start_connect
default 10:11:01.733174 +0800 GoPro Quik 0.190s [C1.1 <private> 192.168.1.6:49983<->IPv4#4fd94374:443 socket-flow] flow:finish_transport
default 10:11:01.733287 +0800 GoPro Quik 0.190s [C1 <private> Hostname#09b7f53c:443 resolver] flow:finish_transport
default 10:11:01.733355 +0800 GoPro Quik 0.509s [C1.1 <private> 192.168.1.6:49983<->IPv4#4fd94374:443 socket-flow] flow:finish_connect
default 10:11:01.733456 +0800 GoPro Quik 0.509s [C1 <private> Hostname#09b7f53c:443 resolver] flow:finish_connect
default 10:11:01.733547 +0800 GoPro Quik 0.509s [C1.1 <private> 192.168.1.6:49983<->IPv4#4fd94374:443 socket-flow] flow:changed_viability
default 10:11:01.733622 +0800 GoPro Quik 0.509s [C1 <private> Hostname#09b7f53c:443 resolver] flow:changed_viability
default 10:11:01.733644 +0800 GoPro Quik 62.170s [C1] path:cancel
default 10:11:01.734082 +0800 GoPro Quik nw_endpoint_flow_protocol_disconnected [C1.1 IPv4#4fd94374:443 cancelled socket-flow (null)] Output protocol disconnected
default 10:11:01.734250 +0800 GoPro Quik nw_connection_report_state_with_handler_locked [C1] reporting state cancelled
default 10:11:01.734285 +0800 GoPro Quik TIC TCP Conn Destroyed [1:0x6000010bdf80]
default 10:11:01.734336 +0800 GoPro Quik nw_socket_handle_socket_event [C1.1:3] Socket received READ_CLOSE event
default 10:11:01.734623 +0800 GoPro Quik nw_socket_handle_socket_event [C2.1:3] Socket received READ_CLOSE event
error 10:11:01.734719 +0800 GoPro Quik nw_protocol_boringssl_get_output_frames(1301) <private>[0x7f9b93301960] get output frames failed, state 8196
error 10:11:01.734753 +0800 GoPro Quik nw_protocol_boringssl_get_output_frames(1301) <private>[0x7f9b93301960] get output frames failed, state 8196
default 10:11:01.735149 +0800 GoPro Quik success removing entry for host <private> config 0x600002598680
error 10:11:01.735187 +0800 GoPro Quik TIC Read Status [2:0x6000010b1980]: 1:57
default 10:11:01.735278 +0800 GoPro Quik TIC TCP Conn Event [2:0x6000010b1980]: 2
error 10:11:01.735303 +0800 GoPro Quik TIC Read Status [2:0x6000010b1980]: 1:57
error 10:11:01.735324 +0800 GoPro Quik TIC Read Status [2:0x6000010b1980]: 1:57
default 10:11:01.735379 +0800 GoPro Quik TIC TCP Conn Cancel [2:0x6000010b1980]
default 10:11:01.735434 +0800 GoPro Quik [C2 Hostname#09b7f53c:443 tcp, url: https://api.gopro.com/v1/locations/geoip.json, tls] cancel
default 10:11:01.735565 +0800 GoPro Quik [C2 Hostname#09b7f53c:443 tcp, url: https://api.gopro.com/v1/locations/geoip.json, tls] cancelled
[C2.1 <private> 192.168.1.6:49984<->IPv4#4fd94374:443]
Connected Path: satisfied (Path is satisfied), interface: en0, ipv4, ipv6, dns
Duration: 61.337s, DNS @0.000s took 0.002s, TCP @0.004s took 0.121s, TLS took 0.260s
bytes in/out: 6075/638, packets in/out: 13/7, rtt: 0.119s, retransmitted packets: 0, out-of-order packets: 0
default 10:11:01.735600 +0800 GoPro Quik 0.000s [C2 <private> Hostname#09b7f53c:443 resolver] path:start
default 10:11:01.735626 +0800 GoPro Quik 0.000s [C2 <private> Hostname#09b7f53c:443 resolver] path:satisfied
default 10:11:01.735652 +0800 GoPro Quik 0.000s [C2 <private> Hostname#09b7f53c:443 resolver] resolver:start_dns
default 10:11:01.735686 +0800 GoPro Quik 0.002s [C2 <private> Hostname#09b7f53c:443 resolver] resolver:receive_dns
default 10:11:01.735729 +0800 GoPro Quik 0.003s [C2.1 <private> 192.168.1.6:49984<->IPv4#4fd94374:443 socket-flow] path:start
default 10:11:01.735755 +0800 GoPro Quik 0.003s [C2.1 <private> 192.168.1.6:49984<->IPv4#4fd94374:443 socket-flow] path:satisfied
default 10:11:01.735774 +0800 GoPro Quik 0.004s [C2.1 <private> 192.168.1.6:49984<->IPv4#4fd94374:443 socket-flow] flow:start_connect
default 10:11:01.735790 +0800 GoPro Quik 0.125s [C2.1 <private> 192.168.1.6:49984<->IPv4#4fd94374:443 socket-flow] flow:finish_transport
default 10:11:01.735863 +0800 GoPro Quik 0.126s [C2 <private> Hostname#09b7f53c:443 resolver] flow:finish_transport
default 10:11:01.735883 +0800 GoPro Quik 0.385s [C2.1 <private> 192.168.1.6:49984<->IPv4#4fd94374:443 socket-flow] flow:finish_connect
default 10:11:01.735941 +0800 GoPro Quik 0.385s [C2 <private> Hostname#09b7f53c:443 resolver] flow:finish_connect
default 10:11:01.736003 +0800 GoPro Quik 0.385s [C2.1 <private> 192.168.1.6:49984<->IPv4#4fd94374:443 socket-flow] flow:changed_viability
default 10:11:01.736070 +0800 GoPro Quik 0.385s [C2 <private> Hostname#09b7f53c:443 resolver] flow:changed_viability
default 10:11:01.736100 +0800 GoPro Quik 61.337s [C2] path:cancel
default 10:11:01.736388 +0800 GoPro Quik nw_endpoint_flow_protocol_disconnected [C2.1 IPv4#4fd94374:443 cancelled socket-flow (null)] Output protocol disconnected
default 10:11:01.736619 +0800 GoPro Quik nw_connection_report_state_with_handler_locked [C2] reporting state cancelled
default 10:11:01.736654 +0800 GoPro Quik TIC TCP Conn Destroyed [2:0x6000010b1980]
error 10:11:01.736675 +0800 GoPro Quik TIC Read Status [1:0x0]: 1:57
error 10:11:01.736690 +0800 GoPro Quik TIC Read Status [1:0x0]: 1:57
error 10:11:01.736751 +0800 GoPro Quik TIC Read Status [1:0x0]: 1:57
error 10:11:01.736789 +0800 GoPro Quik TIC Read Status [1:0x0]: 1:57
default 10:11:01.736932 +0800 GoPro Quik success removing entry for host <private> config 0x60000259c280
error 10:11:01.736967 +0800 GoPro Quik nw_protocol_boringssl_get_output_frames(1301) <private>[0x7f9b9170c650] get output frames failed, state 8196
error 10:11:01.736993 +0800 GoPro Quik nw_protocol_boringssl_get_output_frames(1301) <private>[0x7f9b9170c650] get output frames failed, state 8196
error 10:11:01.737322 +0800 GoPro Quik TIC Read Status [2:0x0]: 1:57
error 10:11:01.737339 +0800 GoPro Quik TIC Read Status [2:0x0]: 1:57
error 10:11:01.737362 +0800 GoPro Quik TIC Read Status [2:0x0]: 1:57
error 10:11:01.737385 +0800 GoPro Quik TIC Read Status [2:0x0]: 1:57

 

Tourist
Posts: 3

Re: Can`t login, still "Authenticating..:" without effect

[ New ]

MY SOLUTION:

I had the same problem, stuck on Authenticating. Tried everything with GoPro support but could not get it to work.

At the end, they said my graphics drivers needing upgrading. I found that hard to believe since my Lenovo Yoga is only 6 months old.

In my case, it was working one day and then suddenly got stuck on Authenticating the next day.

Between these two days I remembered Forticlient did an automatic update.

After UNINSTALLING Forticlient, Quik Desktop is now Authenticating and working fine.

Sightseer
Posts: 1

Re: Can`t login, still "Authenticating..:" without effect

[ New ]

I can't thank you enough. I'm flabbergasted that GoPro can't fix this and that regular users have to do this stuff... but it works. Thanks to you. Much appreciated. Andrew