Troubleshooting Common Problems
Contents
- Common XAMPP and Apache issues
- Common CMS issues
- Troubleshooting SSL encryption
- Troubleshooting .deb or .rpm Installations
Common XAMPP and Apache issues
"It Works" But There Is No Content
If the website at YOU.pagekite.me displays the Apache welcome page, but you cannot access any content, you may need to edit your virtual host configuration to recognize your PageKite name as well as the localhost default.
In some cases, adding these lines to httpd-vhosts.conf may help:
ServerName YOU.pagekite.me
ServerAlias localhost
(Replace the default ServerName settings with these lines.)
In other cases, you may have installed a 3rd party application which has it's own configuration file and a VirtualHost directive which does not match your kite name.
On Linux, the following command may help find some clues:
$ grep -r -e VirtualHost -e ServerName /etc/{apache2,httpd}
Common CMS issues
Cannot access sub-folders, CSS, images do not display.
Similar to the above issue, CMSs such as WordPress and Status.net may also be providing local URLs instead of your PageKite URL. This addressing this is system-dependent, in Status.net it is the
$config['site']['server']
variable in statusnet/config.php.
Troubleshooting SSL encryption
Encryption doesn't work!
.pagekite.me sites
If your website's URL ends in .pagekite.me, then you should be able to use the service's wildcard SSL encryption without any extra effort. However, note that this will only work for pages with exactly two dots in the domain name. So these names are fine:
- foo.pagekite.me
- sub-foo.pagekite.me
But these will not work:
- sub.foo.pagekite.me
- sub.bar.foo.pagekite.me
Other domain names
If your website's name does not end in .pagekite.me, then you will need to provide an SSL certificate of your own and rely on your users to have modern browsers which support the SNI extension of the TLS protocol.
Recent versions of the following browsers are known to work:
- Firefox
- Chrome
- Safari
- Internet Explorer
- curl
The following are do not properly support SNI and will not be able to visit your encrypted site:
- All browsers on Windows XP, except Chrome - Chrome may work
- Konqueror
- wget
Encrypted pages are still considered insecure
If you visit an https:// page and get a security warning or the lock icon appears to be "broken", it may be because you are including images, javascript or CSS from unencrypted sources. Browsers will not consider a page secure unless all elements on the page come from secure sources.
To check if this is the case, you can use the "view source" feature of your browser and search for http://. If it is found in any src= attributes, you will have this problem.
Sub-pages are not encrypted
Some popular software packages, including Wordpress, used hard-coded URLs and may redirect users away from the encrypted site if they have been configured with a normal http:// URL string.
Double check the settings of your software and make sure that all URL paths are configured to use the secure https:// scheme.
"The page isn't redirecting properly" error in browser
It is common for web sites with their own SSL/TLS support to attempt to redirect users which access insecure versions of the site. This can in turn clash with the .pagekite.me, wild-card based encryption, causing an infinite loop of redirection that never successfully completes.
This is because when using the PageKite wild-card certificate, only the connection from the browser to the PageKite front-end relay is encrypted, the traffic seen by your local web-server is plain-text HTTP (although the PageKite connection itself is encrypted, your web server has no way of knowing that).
This problem can be resolved in two ways:
- Disable the redirection in your web application
- Use your own SSL certificate and configure PageKite accordingly
If you already have a local SSL certificate (some systems, such as Yunohost may generate one for you) and an HTTPS-enabled web server on port 443, you can implement solution 2) like so:
pagekite.py --add 443 https://yourkite.pagekite.me/
This will add an HTTPS kite to your ~/.pagekite.rc configuration. If your configuration is in /etc/pagekite.d, then you should instead add a line like this to /etc/pagekite.d/80_httpd.rc:
service_on = https:@kitename : localhost:80 : @kitesecret
Troubleshooting .deb or .rpm Installations
If you are having trouble configuring your integrated Debian or RedHat package, take a look at the troubleshooting section on the ConfigureYourSystem page.
The Beanstalks Project ehf.
Comments
Styles don't load, though, as well as images. Not sure how to resolve this issue.
Any suggestions would be terrific!
Logged on locally from the web server, everything works just fine.
This can be a fair bit of work, but the silver lining is that once you have your local site working flawlessly over PageKite, it will be much easier to actually deploy to a production server (absolute links etc. are a very common problem on newly deployed sites).
I'll get cooking with Firebug to see what requests may not be coming through. Hopefully I can clean some things up and get it working. :)
Thanks a million
$ pagekite.py 9443 yourname.pagekite.me
The site should then become visible as http://yourname.pagekite.me/
If only the front page is visible and links don't work, or javascript/CSS doesn't seem to be loading properly, you may need to review the settings of the webapp and make sure it isn't generating absolute URLs, or worst case update the configuration so it uses the pagekite name instead of localhost:9443 for links.
windows 7 m/c
define('WP_HOME', 'http://' . $_SERVER['HTTP_HOST'] . '');
define('WP_SITEURL', 'http://' . $_SERVER['HTTP_HOST'] . '');
This way the home and siteurl are made automatically, and you can access the site through localhost and pagekite without changing settings. Makes everything a bit slow though, but you can have the localhost or lan ip in the database wp_options, and comment the above lines when you don't need the pagekite.
any ideas
service_on = https:@kitename : localhost:80 : @kitesecret
this should say:
service_on = https:@kitename : localhost:443 : @kitesecret
Beware cut and paste.. has wasted me hours trying track down why it wasnt working.
I also have trouble launching the kites, where 2-3 days ago on trial everything worked fine.
Error says : pagekite.py [down] Disconnected from : http://88.198.105.37:443/
Any help would be appreciated as I got addicted as it allows me to learn mobile development while having a backend to use at the same time.
But it shoots 503 error from all other machine when request is made
Please let us know what went wrong
SyntaxError: Missing parentheses in call to 'exec'
somewhere. I remember seeing it. It involved using Python 2. But I don't see it in any of the usual places.
Maybe it should be.
"kex_exchange_identification: Connection closed by remote host"
My configuration file:
###[ Current settings for pagekite.py v1.0.0.190225. ]#########
#
## NOTE: This file may be rewritten/reordered by pagekite.py.
#
##[ Default kite and account details ]##
kitename = nnnsoma.pagekite.me
kitesecret = a3ezbxkf2k273a9bb663687kfa78kxez
##[ Front-end settings: use pagekite.net defaults ]##
defaults
##[ Back-ends and local services ]##
service_on = http:@kitename : localhost:80 : @kitesecret
service_on = raw-22:@kitename : localhost:22 : @kitesecret
##[ Miscellaneous settings ]##
savefile = /root/.pagekite.rc
###[ End of pagekite.py configuration ]#########
END
I got the same issue from today. I was using pagekite since 6 years, last version being 0.59, all was working fine. During shutdown covid period, i stopped to use it, now i started again today, but impossible to get kites running again. Batch was stuck after the front end adress...
I'm still under Windows XP, using python2.7, with "BitVise SSH Server" in association to an app "connectbot" on a smartphone to create a HTTP tunnel with port redirection.
I then changed to latest version 1.5.2, this ran well but...i got same error message than you guys:
"!!! Failed to connect to 172.105.59.232:443
Unable to verify SSL certificates!
....
"
If you understood the root cause of such failure, and if you know how to workaround it, please let me know.....
Thanks a lot in advance.
Well, for those SSL certificate issues, the solution is to uninstall the old Python2.7.3 version and to install the last one compatible with Windows XP version, meaning the 3.4.4. You delete your old config.cfg file (search in your directories) and then launch again your pagekite.py batch (you will have to confirm some questions from pagekite), then, kites will fly again !
Last point, to be sure that you use the latest version of python, type under a "cmd" (DOS console) the sentence "python --version", it shall display Python 3.4.4, ensuring you have the latest OK version to launch your pakegite.py code.
Thanks !
pagekite.py --add 443 https://yourkite.pagekite.me/
y como estoy usando WordPress, edite el archivo wp-config.php y lo deje de la siguiente manera
if ( !defined('WP_CLI') ) {
define( 'WP_SITEURL', 'https://MySiteName.pagekite.me' );
define( 'WP_HOME', 'https://MySiteName.pagekite.me' );
/** define( 'WP_SITEURL', $_SERVER['REQUEST_SCHEME'] . '://' . $_SERVER['HTTP_HOST'] ); */
/** define( 'WP_HOME', $_SERVER['REQUEST_SCHEME'] . '://' . $_SERVER['HTTP_HOST'] ); */
El sitio finalmente carga PERO tengo algunos problemas, por ejemplo, la pagina carga sin certificado SSL, adicionalmente mi sitio tiene la siguiente estructura:
/config
/controllers
/hekpers
/models
/php
/public
/views
Donde mi pagina principal o de inicio esta en https://MySiteName.me/views/site.php
Pero siempre me aparece el error
Not Found
The requested URL was not found on this server.
Alguien podría darme una mano por favor, muy amables.