Next release of romm should contain fixes for every issue I've found. I'd consider it usable at that point.

I reached out to Romm devs to try and figure out why I'm seeing a bug in my build but not official docker image.(rom with id of 1 won't work with emulator) In the meantime, I tested out netplay and it works! Will update once I hear back.

Okay, I made some more updates today: one step back to take two steps forward. I realized there was another dockerfile in the romm github when trying to figure out why a number of things weren't working. That dockerfile was for production, unlike the one I was looking at. I decided to use more of the processes they have there to try and get the missing features: I needed to use nginx instead of the node dev server and compile some custom modules for nginx. While I was making these changes, I made other parts of the docker build process more mult-stage. The end result is downloading roms and using the emulator work now. Next I'll see what it'll take to get netplay working and check more features out. I feel like I've gotten close to finished!

Made some more progress today: I put some env vars in a file that can be written by user for api keys, added missing workers for jobs, and pulled in precompiled emujs and ruffle from release image. Some things are not set up right still so emujs doesn't work, but one step closer. I'll also look into adding the TURN support for netplay in latest version.

Okay, I made some progress since I last wrote: I fixed some bugs preventing app from working and found a way to get OIDC working too. Now I need to put some effort into using the app and make sure everything is working, especially the remote api services and fix my bad use of secret key.

quick connect would require the client to support quick connect, though. I don't think Home Assistant, for example, supports quick connect.

Thanks, I didn't consider adding a new user, but that seems to have worked. Would be nice to be able to use the exiting user, but this will work.

I put some effort today to package this app. I'm putting a link here to my repo, but it's not complete. Still need to figure out if I can get OIDC working and need to work on the config file and make use of /app/data. I took some ideas from what @murgero last showed and the official romm dockerfile, but built it using cloudron packaging format examples and supervisord.
https://git.cloudron.io/eyecreate/romm
I'll post here when I make any changes. Would love feedback from those knowing more about OIDC how to get it working.

Edit: cloudron gitlab has been spotty so here is a mirror: https://git.eyecreate.org/eyecreate/cloudron-romm

After the migration to OIDC, I've had issues due to a number of jellyfin clients not supporting OIDC. In addition, cloudron only supports app passwords for SFTP, so I can't make an app password for these clients to by pass OIDC. Is there a way to allow using app password with jellyfin for clients who need it?

I have not noticed this issue yet after upgrading to 9.x.

Okay, with 9.0.10, backup was able to be completed.

Do you still want the answers from your first post?

I haven't had a large app backup successfully after 9.0.7. I looked at the logs and saw this message.

/home/yellowtent/box/node_modules/@smithy/smithy-client/dist-cjs/index.js:287
    const response = new exceptionCtor({
                     ^

InvalidArgument: Part number must be an integer between 1 and 10000, inclusive

Would I be able to work around this by increasing the size of upload parts?

Can invidious companion be updated again? I think I'm running into a bug fixed last week.
https://github.com/iv-org/invidious-companion/issues/209

Description

I frequently have the web interface have show apps in old states(like starting or updating). The actual containers are in a different state and once I restart the box service(systemctl restart box), the state shown in the web interface matches again. I've been restarting the service for a few months like this, but figured it would be good to try and hunt down the source of the problem.

Steps to reproduce

Use web interface and see wrong state sometimes.

System Details

Generate Diagnostics Data

Can provide pastebin to support email.

Cloudron Version

v8.3.2

Ubuntu Version

Ubuntu 22.04.5 LTS

Cloudron installation method

• ISO Image?

Output of cloudron-support --troubleshoot

Vendor: GIGABYTE Product: GB-BXi3-5010
Linux: 5.15.0-139-generic
Ubuntu: jammy 22.04
Processor: Intel(R) Core(TM) i3-5010U CPU @ 2.10GHz x 4
RAM: 16194568KB
Disk: /dev/mapper/eyecreate--server--vg-root  431G
[OK]    node version is correct
[FAIL]  Server has an IPv6 address but api.cloudron.io is unreachable via IPv6 (ping6 -q -c 1 api.cloudron.io)

On updating to this version, I get "Error: open test.yml: no such file or directory".

Invidious broke again, but now that inv_sig_helper is archived, it seems cloudron should move to this new tool.

Inv-sig-helper should be updated to dcda9f16ae748639cec652ed504809b60f149e71 to fix a youtube change.

@hakunamatata good call! I didn't guess they would only allow a list of proxy sources. Now the proxy works well!

@nebulon this is all I have:

Response Headers

content-length: 16
content-type: text/plain; charset=utf-8
date: Wed, 11 Jun 2025 18
server: nginx
x-firefox-spdy: h2

400: Bad Request