search

bfabiszewski / ulogger-server

μlogger • web viewer for tracks uploaded with μlogger mobile client
GNU General Public License v3.0
522 stars 85 forks source link

started requiring login but login is turned off. #150

Closed katchy3132 closed 3 years ago

katchy3132 commented 3 years ago

I thought I had things set up to have public tracks but it seems that it started requiring login:

from config table :

public_tracks | b:1; require_auth | b:0;

but in the gui, clicking on settings it has "require auth" checked and "public tracks" not checked.

when I try to change it and click submit , it says "Something went wrong"

bfabiszewski commented 3 years ago

Maybe the table is corrupted? Did you modify it manually? You may try to delete current row from config table. It should be recreated on first save. Of course you will loose all your settings and will have to set them up again in the gui.

katchy3132 commented 3 years ago

I just nuked the entire DB and rcloned the repo. then reran the setup. I was able to login but same thing - I tried changing settings and "Something went wrong. "
I am using MySql.

also shouldn't the user be listed in the dropdown ?
image

bfabiszewski commented 3 years ago

Maybe some problem with database permissions? Which version of the app? Which MySQL version, which PHP version? Check webserver logs and system logs (syslog, messages) for any errors.

katchy3132 commented 3 years ago

I was using the latest git repo. mysql 10.2.35-MariaDB php 7.3.21 that was on a shared hosting provider which is hard to debug.

I just tried again on another machine- using sqlite and got the same "something went wrong"

in the logs I see the following

FastCGI sent in stderr: "PHP message: PHP Notice:  
Undefined variable: lang in /home/ubuntu/ulogger/ulogger-server.git/utils/saveconfig.php on line 26
PHP message: PHP Notice:  
Trying to access array offset on value of type null in /home/ubuntu/ulogger/ulogger-server.git/utils/saveconfig.php on line 26" while reading response header from upstream
bfabiszewski commented 3 years ago

There seems to be a bug that prevents showing proper error message. But it means that somehow your user is not authorized to save config.

katchy3132 commented 3 years ago

I am using the user I created during setup . And I see the settings , add user, and edit user in menu when logged in . in the database the user has a '1' for admin .

bfabiszewski commented 3 years ago

In the meantime I committed a fix to the problem visible in the log file. You may check if it changes anything.

bfabiszewski commented 3 years ago

Also look into system log files other that www/php logs. Ulogger logs its internal errors using syslog with LOG_ERR priority. Depending on OS settings the log messages may land in different files, eg. syslog or messages.

bfabiszewski commented 3 years ago

Now that I think about your issues I realized that you may have problems with PHP sessions. Because it seems that main screen loads with proper permissions after authorization. But any subsequent calls to PHP are probably not authorized. Make sure you have PHP session support installed, properly configured session permissions. And make sure you don't block cookies in your browser.

katchy3132 commented 3 years ago

it must have been some combination of not saving cookies and incorrectly configured logfiles which was causing the process to fail.

thank you!

BTW in settings, the fields for latitude and longitude only take values to 2 decimal places which isn't clear - it wasnt saving at all until i shortened the values.