How do I correctly configure for running YNH with PageKite?

Hi

I am running current stable YNH on an Odroid C2 quite reliably and now tried to access it via PageKite from outside my local network – so far without success.

YNH is configured with the domain odroid.p3k.org which is also set as CNAME for the corresponding p3k.pagekite.me domain.

/etc/pagekite.d/80_httpd.rc contains:

service_on = http:@kitename : localhost:80 : @kitesecret
service_on = https:@kitename : localhost:443 : @kitesecret
service_on = http:odroid.p3k.org : localhost:80 : @kitesecret
service_on = https:odroid.p3k.org : localhost:443 : @kitesecret

Trying to access p3k.pagekite.me results in a security exception thrown by the browser (Chrome), and – after clicking the “proceed (unsafe)” link – either in an unstyled admin interface (first request, probably from cache) or a temporarily unavailable message from PageKite.

The PageKite log shows the following:

ts=5a08371e; t=2017-11-12T12:57:18; ll=e9; err=Error in connect: Traceback (most recent call last):   File "<string>", line 471, in _BackEnd   File "<string>", line 331, in _Connect   File "<string>", line 1028, in connect   File "<string>", line 900, in __negotiatehttpconnect HTTPError: (400, 'Bad Request')
ts=5a08371e; t=2017-11-12T12:57:18; ll=ea; err=Server response parsing failed: (400, 'Bad Request'); id=s4
ts=5a08371e; t=2017-11-12T12:57:18; ll=eb; eof=1; id=s4
ts=5a08371f; t=2017-11-12T12:57:19; ll=ec; connect=94.130.76.112:443
ts=5a08371f; t=2017-11-12T12:57:19; ll=ed; debug=TunnelManager: problem=1, connecting=2
ts=5a083720; t=2017-11-12T12:57:20; ll=ee; FE=94.130.76.112:443
ts=5a083720; t=2017-11-12T12:57:20; ll=ef; FE=94.130.76.112:443; quota=2621081; id=s5
ts=5a083720; t=2017-11-12T12:57:20; ll=f0; FE=94.130.76.112:443; q_conns=5; id=s5
ts=5a083720; t=2017-11-12T12:57:20; ll=f1; FE=94.130.76.112:443; q_days=26; id=s5
ts=5a083720; t=2017-11-12T12:57:20; ll=f2; FE=94.130.76.112:443; proto=https; domain=odroid.p3k.org; ssl=False; id=s5
ts=5a083720; t=2017-11-12T12:57:20; ll=f3; bid=https:odroid.p3k.org; status=0x1000
ts=5a083720; t=2017-11-12T12:57:20; ll=f4; FE=94.130.76.112:443; proto=http; domain=p3k.pagekite.me; ssl=True; id=s5
ts=5a083720; t=2017-11-12T12:57:20; ll=f5; bid=http:p3k.pagekite.me; status=0x11000
ts=5a083720; t=2017-11-12T12:57:20; ll=f6; FE=94.130.76.112:443; proto=https; domain=p3k.pagekite.me; ssl=True; id=s5
ts=5a083720; t=2017-11-12T12:57:20; ll=f7; bid=https:p3k.pagekite.me; status=0x11000
ts=5a083720; t=2017-11-12T12:57:20; ll=f8; FE=94.130.76.112:443; proto=http; domain=odroid.p3k.org; ssl=False; id=s5
ts=5a083720; t=2017-11-12T12:57:20; ll=f9; bid=http:odroid.p3k.org; status=0x1000

Any suggestions what configuration could be missing or incorrect in this case?

Cheers,
tobi