Quote:
Originally Posted by mariosipad
@MontyJ
If you get a "familiar"  error, then PageKite is working (again) 
Does the error looks something like this?
Code:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
The error is caused by a wrong path in AuthUserFile /path/to/.htpasswd in ./web/cops/.htaccess.
The path needs to be an absolute path from the QNAB / to the .htpasswd file.
The line
Code:
AuthUserFile /share/MD0_DATA/.qpkg/COPS/accesCops.htpasswd
must be wrong. (At the very least I am missing a / in front of .htpasswd )
If we want (for the time being) to put .htpasswd in ./web/cops we need to find the absolute path to this location. If you know what it is then disregard the next lines. 
To find out the absolute location of the web root (from there is it ./cops/.htpasswd) please make a file named myroot.php in ./web with this content:
Code:
<html>
<head>
<title>Getting your AuthUserFile root location</title>
</head>
<?php
echo "<h1>Your website root location is --> ";
echo $_SERVER['DOCUMENT_ROOT'];
echo " <--<h1/>";?>
<body>
</body></html>
then in a browser http://192.168.xxx.xxx/myroot.php.
Note the web root between -> /Y/Y/Y <-.
Now go to ./web/cops and edit .htaccess. The last few lines must now look like (where you fill in /Y/Y/Y (starting with the /) 
Code:
###########################################
# Uncomment if you wish to protect access with a password
###########################################
# If your covers and books are not available as soon as you protect it
# You can try replacing the FilesMatch directive by this one
# <FilesMatch "(index|feed)\.php">
# If helps for Sony PRS-TX and Aldiko, beware fetch.php can be accessed
# with authentication (see $config ['cops_fetch_protect'] for a workaround).
###########################################
<FilesMatch "\.php$">
AuthUserFile "/Y/Y/Y/cops/.htpasswd"
AuthGroupFile /dev/null
AuthName "Secure access"
AuthType Basic
Require valid-user
</FilesMatch>
Did this help?
The unexpected error kept me baffled for a while as well.  |
Good morning, afternoon, evening...where ever you may be, LoL!
Ok, the result of myroot.php is: Your website root location is --> /share/Web <--
When I put that in my .htaccess file, here are the lines in total:
Code:
<FilesMatch "\.php$">
AuthUserFile "/share/Web/cops/.htpasswd"
AuthGroupFile /dev/null
AuthName "Acces securise"
AuthType Basic
Require valid-user
</FilesMatch>
The only thing different is AuthName "Access securise", which I assume is French for "Secure Access". Does that make a diff? Should I change it?
In any case I still get the "500 Internal Server Error", and the browser url window changed to "http://mydomain.pagekite.me/cops/"
[edit] Here are the terminal results when I run pagekite and then try to login:
Code:
[/share/Web] # python pagekite.py --optfile=/share/Web/pagekite.rc mydomain.pagekite.me
>>> Hello! This is pagekite.py v0.5.9.0. [CTRL+C = Stop]
Connecting to front-end relay 54.183.178.65:443 ...
- Protocols: http http2 http3 https websocket irc finger httpfinger raw
- Protocols: minecraft
- Ports: 79 80 443 843 2222 3000 4545 5222 5223 5269 5670 6667 8000 8080
- Ports: 8081 9292 25565
- Raw ports: 22 virtual
Quota: You have (my acct data) connections left.
~<> Flying localhost:80 as https://mydomain.pagekite.me/
!!! xxx.xxx.xxx.xxx - http://mydomain.pagekite.me:80 (USER ACCESS DENIED)
xxx.xxx.xxx.xxx < http://mydomain.pagekite.me:80 (localhost:80)
<< pagekite.py [flying] Kites are flying and all is well.
Interesting...I just noticed a pagekite version change. I had sent him/them(?) a descriptive email on the problems and a request for help 2 days ago. Maybe he got out of the hot lava thermal pool to check on things?...
