RetroPie-Manager web app (Recalbox-Manager fork/mod)

[meleu]

@robertybob look at your /home/pi/RetroPie-Setup/logs/ ;-)
The RetroPie-Setup logs are named as rps_TIME_STAMP.log.gz and are gziped, but you can read it with the zless command.

[larryd85]

@meleu said in RetroPie-Manager web app (Recalbox-Manager fork/mod):

/home/pi/RetroPie-Setup/logs/

i am running into the same problem
here is my log from trying to update the package through the retropie setup

http://pastebin.com/ZJv8UTFT

[BuZz]

Did you have it installed before? If so please try removing then re-installing as I changed the module install method which is incompatible with the old one when it was first added. I've not had a chance to look yet though if there is another issue.

[BuZz]

Installed fine here (and updated fine after). I suspect you just need to remove and reinstall - then it should be good for future upgrades.

[larryd85]

@BuZz i removed the package and then reinstalled it, here is the log from re-installing.
http://pastebin.com/UQcH4rkc
i still get "A server error occurred. Please contact the administrator." when i try to connect through chrome

[BuZz]

the install issue is different from that error. I am looking into that.

[BuZz]

The previous module installed the requisites system wide afair, and I changed it to not do this but to install correctly just in the install folder. I missed the fact that the rpmanager.sh doesn't initialise the python virtualenv - it will need the addition to do this.

source /opt/retropie/supplementary/retropie-manager/bin/activate before running. I'll fork it and do the code and submit a PR.

[BuZz]

I don't have more time to do this right now, so I will look further in a bit (unless someone else wants to have a go). I missed this when I converted the module, as it had already installed the requirements system wide. As this is a retropie module we want to be able to "remove" I changed that so it just needs adjusting to work via the virtualenv.

[BuZz]

Sorry, my mistake, the env was ok - I just thought it wasn't due to my debugging.

Looks like django security is at play in the current version

following changes sort it for me (to access via http://retropie:8000/)

see - https://docs.djangoproject.com/en/1.10/ref/settings/

Changed in Django 1.10.3:
In older versions, ALLOWED_HOSTS wasn’t checked if DEBUG=True. This was also changed in Django 1.9.11 and 1.8.16 to prevent a DNS rebinding attack.

and we use django 1.8.16 now.

so we will need to put the retropie name in here.

--- a/project/settings.py
+++ b/project/settings.py
@@ -39,7 +39,7 @@ SECRET_KEY = '(_0!&^^xekahfp=s5(9+^wlq6gvn6z90%i*p+wn^4ir+mvl4lx'
 # SECURITY WARNING: don't run with debug turned on in production!
 DEBUG = True
 
-ALLOWED_HOSTS = []
+ALLOWED_HOSTS = ['retropie']
 
 
 # Application definition

there may be a way to disable this check also.

[detron]

I appreciate the hard work that the people behind the scenes of RetroPie put into fixing issues.
I was just coming here to ask what I was doing wrong, but see others already had mentioned the same issue, and the fix is on the way!

bravo!

[meleu]

I've just fixed the settings.py, but I used ALLOWED_HOSTS = ['*']. It worked well in my tests.

Please update your retropie-manager and let me know if it stills happening.

Thanks BuZz for pointing the reason of the problem.

[larryd85]

yup, i can connect now. thanks for the great tool!

[BuZz]

Cheers!

[robertybob]

Thanks guys, I'll get onto my Pi tomorrow night and reinstall this :)

[robertybob]

Finally got around to trying this out, OMG it's amazing! Such a great tool for noobs that I think it should be enabled by default (or at least installed by default and the option to enable isn't buried deep within the Setup Scipt).

[meleu]

@robertybob Unfortunately the development seems to be dead. @Botolo is the guy that forked it from recalbox and was playing with the code. Currently he seems to be busy and doesn't appear around here.

I contributed with testing, wrote the rpmanager.sh and finished the scriptmodule started by @herb_fargus .

RetroPie-manager has some limitations/bugs/issues and unfortunately I'm not able to code web/python/Django stuff to improve it. @Botolo gave me access to the repository when it started and I was able to fix this recent ALLOWED_HOSTS issue. Otherwise we would have to abandon (or fork) the retropie-manager.

Well... I told this story to justify my opinion that RetroPie-manager should stay at experimental packages. Because it is indeed experimental.

[meleu]

By the way: @fechy started a similar tool from scratch. Look this topic: https://retropie.org.uk/forum/topic/4627/retropie-web-gui

It has less features, but at least the development can be more active if he receive users feedback.