Can't connect to Google Calendar via IPv6 #17

hanskokx · 2018-05-17T20:23:08Z

Unable to configure Google Calendar. A code is never generated.

qml: HTTP 0 Headers: 

file:///home/hans/.local/share/plasma/plasmoids/org.kde.plasma.eventcalendar/contents/ui/config/GoogleCalendarSession.qml:69: SyntaxError: JSON.parse: Parse error
qml: HTTP 0 Headers: 

file:///home/hans/.local/share/plasma/plasmoids/org.kde.plasma.eventcalendar/contents/ui/config/GoogleCalendarSession.qml:69: SyntaxError: JSON.parse: Parse error
qml: HTTP 0 Headers: 

file:///home/hans/.local/share/plasma/plasmoids/org.kde.plasma.eventcalendar/contents/ui/config/ConfigSerializedString.qml:15: SyntaxError: JSON.parse: Parse error
file:///home/hans/.local/share/plasma/plasmoids/org.kde.plasma.eventcalendar/contents/ui/config/ConfigGoogleCalendar.qml:28: TypeError: Cannot call method 'concat' of undefined

The text was updated successfully, but these errors were encountered:

Zren · 2018-05-17T20:57:04Z

Are you offline?
What version of Event Calendar?
What distro? What version of Qt? What version of Plasma? To find out, open the Info Center app.

hanskokx · 2018-05-17T21:11:14Z

No, I'm not offline. Version 56; pulled from git and did a reinstall. Kubuntu 18.04; KDE Plasma 5.12.4; Qt 6.9.5

…

On Thu, May 17, 2018 at 4:57 PM Chris Holland ***@***.***> wrote: - Are you offline? - What version of Event Calendar? - What distro? What version of Qt? What version of Plasma? To find out, open the Info Center app. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#17 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB0sbxaesOsV6x2qWKTTVwLucqgnzcgiks5tzeQggaJpZM4UDt1m> .

Zren · 2018-05-17T21:59:08Z

Try relogging when you get the chance.

hanskokx · 2018-05-17T22:00:49Z

I did that several times. I also removed/reinstalled.

…

-- Hans Kokx On 5/17/2018 5:59:09 PM, Chris Holland <[email protected]> wrote: Try relogging when you get the chance. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [#17 (comment)], or mute the thread [https://github.com/notifications/unsubscribe-auth/AB0sbx4YAGCzgt4AA0U97vd7hBPB3XA6ks5tzfKtgaJpZM4UDt1m].

Zren · 2018-05-17T22:38:48Z

I tried in KDE Neon, and with the Kubuntu 18.04 LiveCD in VirtualBox, and it still works for me.

HTTP 0 usually means it can't send the request (eg: offline), or there was some other error making the connection via Qt. Hmmm...

hanskokx · 2018-05-17T22:39:58Z

What's it trying to connect to? I was noticing some weird issues trying to ping my server remotely (IPv6). Could possibly be some network weirdness. If I knew what host, I could investigate that further.

…

-- Hans Kokx On 5/17/2018 6:38:49 PM, Chris Holland <[email protected]> wrote: I tried in KDE Neon, and with the Kubuntu 18.04 LiveCD in VirtualBox, and it still works for me. [https://camo.githubusercontent.com/0c19edad48effe4ca7515efcdd5c2b739b08cd95/68747470733a2f2f692e696d6775722e636f6d2f56784658427a472e706e67] HTTP 0 usually means it can't send the request (eg: offline), or there was some other error making the connection via Qt. Hmmm... — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [#17 (comment)], or mute the thread [https://github.com/notifications/unsubscribe-auth/AB0sb-5HQfgiJdpuvvJlZHP35_-v8B6Xks5tzfv4gaJpZM4UDt1m].

Zren · 2018-05-17T22:47:00Z

You could turn on debugging (at the bottom of Event Calendar > General) to log the json responses it does receive.

It first connects to https://accounts.google.com/o/oauth2/device/code to get the "code", then it checks https://www.googleapis.com/oauth2/v4/token every 5 seconds to see if the user has logged in yet. After you've logged in and it's successfully received an Access Token, it contacts https://www.googleapis.com/calendar/v3/users/me/calendarList to get your list of calendars.

https://github.com/Zren/plasma-applet-eventcalendar/blob/master/package/contents/ui/config/GoogleCalendarSession.qml#L57

Zren · 2018-05-17T22:48:16Z

See if you can connect to those hosts with both IPv4 and IPv6.

hanskokx · 2018-05-18T13:43:55Z

So, here's what I'm seeing: [ 9:40 AM] hans@hans-linux-vm ~ $ nc -vzw 2 accounts.google.com 443 nc: connect to accounts.google.com port 443 (tcp) timed out: Operation now in progress Connection to accounts.google.com 443 port [tcp/https] succeeded! [ 9:40 AM] hans@hans-linux-vm ~ $ nc -vzw 2 www.googleapis.com 443 nc: connect to www.googleapis.com port 443 (tcp) timed out: Operation now in progress Connection to www.googleapis.com 443 port [tcp/https] succeeded! [ 9:41 AM] hans@hans-linux-vm ~ $ ping accounts.google.com PING accounts.google.com(ord38s18-in-x0d.1e100.net (2607:f8b0:4009:804::200d)) 56 data bytes ^C --- accounts.google.com ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1027ms [ 9:41 AM] hans@hans-linux-vm ~ $ ping -4 accounts.google.com PING accounts.google.com (172.217.4.45) 56(84) bytes of data. 64 bytes from lga15s46-in-f13.1e100.net (172.217.4.45): icmp_seq=1 ttl=54 time=9.75 ms 64 bytes from lga15s46-in-f13.1e100.net (172.217.4.45): icmp_seq=2 ttl=54 time=10.1 ms ^C --- accounts.google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 9.750/9.945/10.140/0.195 ms [ 9:41 AM] hans@hans-linux-vm ~ $ ping www.googleapis.com PING www.googleapis.com(ord30s21-in-x0a.1e100.net (2607:f8b0:4009:80a::200a)) 56 data bytes ^C --- www.googleapis.com ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1027ms [ 9:41 AM] hans@hans-linux-vm ~ $ ping -4 www.googleapis.com PING googleapis.l.google.com (172.217.0.10) 56(84) bytes of data. 64 bytes from ord38s04-in-f10.1e100.net (172.217.0.10): icmp_seq=1 ttl=54 time=10.3 ms ^C --- googleapis.l.google.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 10.315/10.315/10.315/0.000 ms [ 9:42 AM] hans@hans-linux-vm ~ $ Looks like I can hit it, but IPv4 only. I can try switching this VM to NAT instead of bridged mode to see if that impacts things ¯\_(O_o)_/¯

…

On Thu, May 17, 2018 at 6:48 PM Chris Holland ***@***.***> wrote: See if you can connect to those hosts with both IPv4 and IPv6. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#17 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB0sb70SRVGle_fvE4HnUbVUnsnmCbiXks5tzf4xgaJpZM4UDt1m> .

hanskokx · 2018-05-18T13:46:15Z

That does appear to fix it, but it's only a temporary solution for me as I need to be NATed. At least I know what the problem is and can address it. Thanks for the support -- maybe look into improving error handling?

…

On Fri, May 18, 2018 at 9:43 AM Hans Kokx ***@***.***> wrote: So, here's what I'm seeing: [ 9:40 AM] ***@***.*** ~ $ nc -vzw 2 accounts.google.com 443 nc: connect to accounts.google.com port 443 (tcp) timed out: Operation now in progress Connection to accounts.google.com 443 port [tcp/https] succeeded! [ 9:40 AM] ***@***.*** ~ $ nc -vzw 2 www.googleapis.com 443 nc: connect to www.googleapis.com port 443 (tcp) timed out: Operation now in progress Connection to www.googleapis.com 443 port [tcp/https] succeeded! [ 9:41 AM] ***@***.*** ~ $ ping accounts.google.com PING accounts.google.com(ord38s18-in-x0d.1e100.net (2607:f8b0:4009:804::200d)) 56 data bytes ^C --- accounts.google.com ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1027ms [ 9:41 AM] ***@***.*** ~ $ ping -4 accounts.google.com PING accounts.google.com (172.217.4.45) 56(84) bytes of data. 64 bytes from lga15s46-in-f13.1e100.net (172.217.4.45): icmp_seq=1 ttl=54 time=9.75 ms 64 bytes from lga15s46-in-f13.1e100.net (172.217.4.45): icmp_seq=2 ttl=54 time=10.1 ms ^C --- accounts.google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 9.750/9.945/10.140/0.195 ms [ 9:41 AM] ***@***.*** ~ $ ping www.googleapis.com PING www.googleapis.com(ord30s21-in-x0a.1e100.net (2607:f8b0:4009:80a::200a)) 56 data bytes ^C --- www.googleapis.com ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1027ms [ 9:41 AM] ***@***.*** ~ $ ping -4 www.googleapis.com PING googleapis.l.google.com (172.217.0.10) 56(84) bytes of data. 64 bytes from ord38s04-in-f10.1e100.net (172.217.0.10): icmp_seq=1 ttl=54 time=10.3 ms ^C --- googleapis.l.google.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 10.315/10.315/10.315/0.000 ms [ 9:42 AM] ***@***.*** ~ $ Looks like I can hit it, but IPv4 only. I can try switching this VM to NAT instead of bridged mode to see if that impacts things ¯\_(O_o)_/¯ On Thu, May 17, 2018 at 6:48 PM Chris Holland ***@***.***> wrote: > See if you can connect to those hosts with both IPv4 and IPv6. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#17 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AB0sb70SRVGle_fvE4HnUbVUnsnmCbiXks5tzf4xgaJpZM4UDt1m> > . >

intika · 2019-02-09T09:51:05Z

Had similar issue, actually it's not related to network at all... even if the bug is blocking network XMLHttpRequest... in my case it was caused by a mis configuration related to another plasmoid (notifications) what i did is remove the plasmoid that caused the problem restart plasmashell then added back the removed plasmoid.

How to debug - Detailed solution

Make a copy of plasma desktop main config file : /home/user/.config/plasma-org.kde.plasma.desktop-appletsrc
Start a temporary french desktop (with the steps bellow)
Kill plasmashell, remove /home/user/.config/plasma-org.kde.plasma.desktop-appletsrc, start plasmashell and check if it works as intended (if it works this mean it's related to a plasmoids in this case follow the rest of the steps, but if it does not work here it mean that the problem come from somewhere else may be a missing/corrupted package... in that case restore your config file and debug differently...)
Restore plasma-org.kde.plasma.desktop-appletsrc and restart plasmashell
Remove suspected plasmoid and restart plasmashell (repeat this step until it works and you identify the guilty plasmoid)
Restore plasma-org.kde.plasma.desktop-appletsrc and restart plasmashell
Remove the guilty plasmoid
Restart plasmashell
Restore the removed plasmoid

Zren changed the title ~~Unable to configure Google Calendar~~ Can't connect to Google Calendar via IPv6 May 18, 2018

Zren mentioned this issue May 18, 2018

Improve Error Handling #18

Open

Zren mentioned this issue Dec 5, 2019

Google Calendar integration #108

Open

drmhessler mentioned this issue Oct 28, 2020

crashes plasmashell when go to settings after upgrading to kubuntu 20.10 #167

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Can't connect to Google Calendar via IPv6 #17

Can't connect to Google Calendar via IPv6 #17

hanskokx commented May 17, 2018

Zren commented May 17, 2018

hanskokx commented May 17, 2018 via email

Zren commented May 17, 2018

hanskokx commented May 17, 2018 via email

Zren commented May 17, 2018

hanskokx commented May 17, 2018 via email

Zren commented May 17, 2018

Zren commented May 17, 2018

hanskokx commented May 18, 2018 via email

hanskokx commented May 18, 2018 via email

intika commented Feb 9, 2019

Can't connect to Google Calendar via IPv6 #17

Can't connect to Google Calendar via IPv6 #17

Comments

hanskokx commented May 17, 2018

Zren commented May 17, 2018

hanskokx commented May 17, 2018 via email

Zren commented May 17, 2018

hanskokx commented May 17, 2018 via email

Zren commented May 17, 2018

hanskokx commented May 17, 2018 via email

Zren commented May 17, 2018

Zren commented May 17, 2018

hanskokx commented May 18, 2018 via email

hanskokx commented May 18, 2018 via email

intika commented Feb 9, 2019