Muximux icon indicating copy to clipboard operation
Muximux copied to clipboard

Warning: file_get contents(): cannot be empty on line 1122

Open pyrostic opened this issue 7 years ago • 9 comments

I turned authorization on and when I go to the homepage I get the following warning:

Warning: file_get_contents(): Filename cannot be empty in E:\caddy\html\muximux.php on line 1122

pyrostic avatar Feb 15 '17 23:02 pyrostic

Pretty big newb, but stackoverflow leads me to believe its a case issue, should be $FileName not $FileName

pyrostic avatar Feb 15 '17 23:02 pyrostic

Err. FileName not Filename (auto correct got me).

pyrostic avatar Feb 15 '17 23:02 pyrostic

Not sure why but my password isn't working either, I'm doing this all on mobile.

pyrostic avatar Feb 16 '17 00:02 pyrostic

For what it's worth, I experienced this same behavior after adding authentication.

I can reproduce the error after modifying my authentication settings, saving and reloading the settings. At this point I am prompted to enter my username and password. Then, after submitting my credentials, this error appears. (Sometimes I can actually see the error behind the password overlay, prior to submitting my name/pw.)

However, if I reload the browser after the error appears (after already signing in), the muximux interface loads fine.

@pyrostic I had copied the settings.ini.php-example to a new "settings.ini.php" file, prior to loading muximux on my first run. When I opened settings for the first time, the name was already set to "admin" and the password was set to "muximux" as these were what was used in the example. If you did the same, perhaps your password never actually got changed when you hit save and reload.

thedennyk avatar Feb 21 '17 04:02 thedennyk

Perhaps. I'm running this on CaddyServer, along with Organizr and am constantly running into php issues on both. I'm about to potentially switch to Nginx if I can find a good config example, and SSL I don't have to babysit.

On Mon, Feb 20, 2017, 10:29 PM thedennyk [email protected] wrote:

For what it's worth, I experienced this same behavior after adding authentication.

I can reproduce the error after modifying my authentication settings, saving and reloading the settings. At this point I am prompted to enter my username and password. Then, after submitting my credentials, this error appears. (Sometimes I can actually see the error behind the password overlay, prior to submitting my name/pw.)

However, if I reload the browser after the error appears (after already signing in), the muximux interface loads fine.

@pyrostic https://github.com/pyrostic I had copied the settings.ini.php-example to a new "settings.ini.php" file, prior to loading muximux on my first run. When I opened settings for the first time, the name was already set to "admin" and the password was set to "muximux" as these were what was used in the example. If you did the same, perhaps your password never actually got changed when you hit save and reload.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/mescon/Muximux/issues/136#issuecomment-281242645, or mute the thread https://github.com/notifications/unsubscribe-auth/AESUk10htOMMpdG5NcV8ssf92TWESCGjks5remgzgaJpZM4MCX8Q .

pyrostic avatar Feb 21 '17 04:02 pyrostic

same behavior here, as soon as authentication is activated this error appear and login is impossible

gsemet avatar Mar 12 '17 10:03 gsemet

+1 ...any update on this?

ethanopp avatar Aug 11 '17 01:08 ethanopp

Well, that sucks. I did a dumb thing, and associated the filename of the theme file with the Capitalized title displayed in the UI.

Working on a rewrite - this has been fixed in the uncommitted code I have sitting around. Will close and comment when fixed.

d8ahazard avatar Aug 23 '17 01:08 d8ahazard

Any update on this?

Rsslone avatar Dec 12 '17 16:12 Rsslone