Raspberry Pi can't access Max2Play web interface

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 Moderator 5 months, 1 week ago.

Viewing 9 posts - 1 through 9 (of 9 total)
  • 2. Dezember 2018 at 6:14 #42467

    interesting.

    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

    Hi radiomog,

    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?

    TIA

    • This reply was modified 5 months, 2 weeks ago by  Weka_1.
    11. Januar 2019 at 16:55 #43532

    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

    Hi,
    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

    Hi weka,

    We recommend using Class 10 write speed, at least.

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic.

Register here