[Bug]: 2.0.10 + MonsterPi 1.0.4 OR OneClickInstall problems with custom username

[IZA09]

Checkboxes

• I agree to follow our Code of Conduct.
• I have verified no other issues exist related to my request.

What You Are Seeing?

after installing Monster (both attempts via through image 1.0.4 and manual "Quick install" through stock PiOSLite), the data/home and install directories are empty, using WinSCP as well as just attempting to use "fdmm" commands returns a doesn't exist error.

What is Expected?

A populated fdmMonster instance.

How Did You Get This To Happen?

Custom image

• Flashed 32gb sd card with MonsterPi 1.0.4
• fired up Raspberry Pi 3b+
• local webpage reported Monsterpi was installed nut the server itself wasnt running, asked to wait and refresh
• nothing for a while
• WinSCP revealed nothing was actually in ~/.fdm-monster

Linux installer

• flashed 32gb sd card with Pi OS Lite (64-bit)
• fired up Raspberry Pi 3b+
• SSH'd into pi and ran "Quick install" curl command
• ran and installed supposedly without error
• "FDM Monster v2.0.10 is ready"
• server as well as fdmm commands return nothing, this time not even the local webpage comes up
• WinSCP revealed nothing was actually in ~/.fdm-monster

System Details

• Operating System and version: Windows 11
• FDM Monster Installation Method: both MonsterPi 1.0.4 / Quick Install (Linux)
• FDM Monster Server version:
• FDM Monster Client version:
• Middleware: Raspberry Pi 3b+
• Middleware version: n/a

Additional Context

I admit im fledgling with Linux so i may be missing something, i apologize if this isnt a bug and just user error.

[davidzwa]

Hi, I'm sorry to hear that this didn't go as smooth as designed. I have some questions.

Which imager did you use to flash the custom and base image?
Which user did you configure and which user are you installing with? The command-line interface will take into account the current user, and the MonsterPi image was built with the pi user in mind.
So if you're checking for example the root's ~/.fdm-monster that would not exist.

And it's not clear to me from your notes: did you at any point see the webpage for FDMM load?

Did you try this on a Pi4 or 5? I have never actually tested both approaches on a Pi3b+.

[IZA09]

Which imager did you use to flash the custom and base image? Which user did you configure and which user are you installing with? The command-line interface will take into account the current user, and the MonsterPi image was built with the pi user in mind. So if you're checking for example the root's ~/.fdm-monster that would not exist.

And it's not clear to me from your notes: did you at any point see the webpage for FDMM load?

Did you try this on a Pi4 or 5? I have never actually tested both approaches on a Pi3b+.

• i used Pi imager v2.0.6
  • i did use a custom names which may infact be the issue, ill have to retry with stock pi user and report back
• i did not save a screenshot unfortunatly, but i never reached the actual "homepage". the page i reached was one saying Monster was installed but the server was not running - it was a simple all white with the logo at the top left corner if i recall. i could probably replicate the issue just to give you a screenshot if youd like.
• no i did not try on a 4 or 5 as i only have a 3b+. the documentation implied pi3 was compatible, even warning that pi5 was not.

[IZA09]

Ok I got it running. I seemed the issue was that i was using a custom pi username/password. I used all defaults and it seemed to have gone through correctly.

Note that this was through PiOSLite and running the installer from within.

I would maybe add compatibility for custom names? or make it more clear that you cant. the documentation mentioned that i could use a different name but apparently that wasn't true.

https://docs.fdm-monster.net/docs/installing/monsterpi

11. In the General section, check the checkbox for Set Hostname and name it monsterpi.

! info You can pick any name, but that will change steps later in the documentation

and as for this, maybe i didnt understand it correctly but i thought this meant it would revert the fields back to default which is why i never changed them back officially:

Also check the Set username and password checkbox. Set the username to pi and the password to any value. This is required for enabling SSH later on.

Note: You cannot change the default username and password using the Raspberry Pi Imager. The default username and > password will still be pi and raspberry. This is due to a limitation of using Ubuntu instead of RaspberryPiOS.

[davidzwa]

Just moved this to the MonsterPi repo.

Nice Im glad you got it figured out! Can you clarify whether it was the hostname or the username/password which seemed to have caused this?

About the documentation: the page is outdated. That's something I will tackle immediately.

[davidzwa]

fdm-monster/fdm-monster-docs#313

[IZA09]

Nice Im glad you got it figured out! Can you clarify whether it was the hostname or the username/password which seemed to have caused this?

that i unfortunately cant say as i had reverted both at the same time, though im pretty sure it was the hostname as when i used an hdmi to monitor its startup of the Monsterpi image, the automated login using my custom fields went smoothly until it actually went to install where im guessing it was looking for "monsterpi" and didnt see it but chugged through regardless without any error or warnings.

I appreciate the quick responses and if needed i dont mind reproducing any of the issues for proof or reference if needed.