Max2Play Home 2016 (en) › Forums › Max2Play on Raspberry PI › Raspberry Pi can't access Max2Play web interface
This topic contains 8 replies, has 3 voices, and was last updated by Heiner premium 4 years, 2 months ago.
Posted in: Max2Play on Raspberry PI
2. Dezember 2018 at 6:08 #42466
I had to re-image the SD card today on one of my Raspberry Pi’s, (using M2P v 2.47)
After power up, I accessed the Max2Play interface and set up my IQaudIO card and registered the software, no problem.
The settings changes required the RPi to be rebooted, so I clicked on the link to do so. M2P rebooted.
The device shows up in my LMS player list and everything on the player side seems to be working just fine.
The problem I’m encountering, is that when I try and access the Max2play web interface (using the name and/or IP address), I get the following message in my browser:
This site can’t be reached The webpage at http://max2play2/ might be temporarily down or it may have moved permanently to a new web address.
using IP address:
This site can’t be reached 192.168.0.42 refused to connect.
Checking the connection
Checking the proxy and the firewall
I have 3 total devices (RPi) running M2P, The other two devices, not effected by the problem, allow me access to their M2P web interfaces (both IP and/or Names). I also note that in the upper right corner of the web interface, there is the shortcut to the other devices. the unit with the ’new‘ install doesn’t show up at all.
I tried to access the problem RPi with ssh (via a linux machine) and I get a „Permission denied, please try again“
I think this problem occurred earlier this year, when I had a similar problem, which was resolved (?)
(How, I don’t remember and a search of the site didn’t provide any clues)
This is NEW behavior for M2P, everything seemed to work properly, with a fresh install, without issue, before 2018 (best I can remember)2. Dezember 2018 at 6:14 #42467
I was unable to SSH into the other Max2Play device I re-imaged earlier this year,
The Server Rpi does accept ssh access.
All three of these units are running stock M2P software, so the default user/pw combo should work .4. Dezember 2018 at 16:04 #42536
The SSH login should be user: pi pw: max2play and if you want to execute as superuser/root, you need to execute „sudo su“ and use pw max2play again.11. Januar 2019 at 0:44 #43434
I have the same problem after one reboot. Through the tv i can see the linux desktop is running perfectly. But i can’t login or use
SSH to open the interface. If i cut the power completely for at least 10 seconds this usually allows me to login after I restart it. My questions are:
How to check if the Max2Play process is running?
Where is it in the linux file system?
How to start it?
11. Januar 2019 at 16:55 #43532
- This reply was modified 4 years, 2 months ago by Weka_1.
Weka and radiomog,
Please check your Password Protection Plugin and make sure SSH is running with a process ID.12. Januar 2019 at 5:31 #43547
I believe I have found a partial solution to my own problem.
When I had ssh running on my macbook and checking running processes. I could see Apache2 webserver had stopped after a reboot.
When I start Apache2 via SSH. I can immediately login as normal.13. Januar 2019 at 6:11 #43563
Another soft reboot and can’t access Max2Play web interface
[email protected]:/etc/default# service –status-all
[ – ] alsa-utils
[ + ] apache-htcacheclean
[ – ] apache2
[ + ] avahi-daemon
[ + ] bluetooth
[ – ] console-setup.sh
[ + ] cron
[ + ] dbus
[ – ] dhcpcd
[ – ] dnsmasq
[ + ] dphys-swapfile
[ + ] fake-hwclock
[ ? ] gmediarender
[ + ] hd-idle
[ + ] hddtemp
[ + ] hostapd
[ – ] hwclock.sh
[ + ] ifplugd
[ ? ] init-ympd
[ – ] keyboard-setup.sh
[ + ] kmod
[ ? ] librespot
[ + ] lightdm
[ + ] lircd
[ + ] lircmd
[ + ] lm-sensors
[ + ] logitechmediaserver
[ + ] minidlna
[ – ] mpd
[ + ] networking
[ – ] nfs-common
[ – ] nmbd
[ – ] paxctld
[ – ] plymouth
[ – ] plymouth-log
[ + ] procps
[ + ] raspi-config
[ – ] rpcbind
[ – ] rsync
[ + ] rsyslog
[ – ] samba
[ – ] samba-ad-dc
[ ? ] shairport
[ + ] shellinabox
[ – ] smbd
[ ? ] squeezelite
[ + ] ssh
[ – ] sudo
[ + ] triggerhappy
[ + ] udev
[ – ] x11-common
Apache2 not running. But why did it not restart?14. Januar 2019 at 5:39 #43567
Someone suggested that the memory card that I was using was too slow. I found another that is working quicker. After a few tests it
is definitely much better. Apache2 is restarting almost every time.
I will try to get an even better card and see what happens from there.
Max2play didnt supply my original card.
I was using one of my own.14. Januar 2019 at 16:13 #43610
We recommend using Class 10 write speed, at least.
You must be logged in to reply to this topic.