avinyc

It just needed time to populate I guess, all working on its own now. Thank you!

I just upgraded today from 6.12.15 to 7.0.1. and I see the same issue with the newly enabled Virtual Machines Usage window on the dashboard. The usage stats are showing in VM Usage Statistics window on the VMS tab. Not sure if this is something that needs time to populate, but I tried shutting down all vms and disabling and enabling VM Manager but it is still showing Loading... for all vms on the dashboard.

It's better that you added one for community apps. One correction: line 4 of the XML link is misspelled: <TemplateURL>https://raw.githubusercontent.com/corgan2222/unraid-templates/main/ManictimeServer/ManictimeServerox.xml</TemplateURL> The link should be "/ManictimeServer.xml" without the "ox" for the template URL.

Gotcha, I assumed they were pulling the same images but you are right, it is a forked repo so that would explain why the same settings were not getting this to work for me on the different templates. When I run the container, it shows v Latest Build - 2024-11-23 on the login page and the about page says v5.10.55. If you ever figure out how to get this consistently working, I may give it another try. Good luck!

I took the plunge to install this after being disappointed with akaunting. I got this working using the anojht/invoiceninja template (tried the official and the v5, but kept running into problems during setup). When I saw this also required an annual license to remove branding, I stumbled across InvoiceShelf which I think is a better option. The template has some errors but I managed to fix it to get things up and running. Back to invoiceninja, using the anojht/invoiceninja repo, this container is very sensitive to the order of operations during the installation phase. I used Adminer to set up the database for mysql and add the user before running the container install. Some of the setup instructions for synology are helpful for setting up the directories and generating the appkey: https://mariushosting.com/how-to-install-invoice-ninja-on-your-synology-nas/ The reverse proxy setup is similar to all other containers, so no special steps needed, but getting this one to work you have to make sure everything is done in the proper order or else you have to start fresh to get it running.

If anyone else sees this thread and wants to add this to their server, it is now showing on CA thanks to @corgan including the template in his repo. The support thread can be found here:

Thank you for adding this to your repo. I had to set this up manually a few years back, and it's been working perfectly for me. It's a great product for timekeeping, and the developer was nice to help me get this working on docker and reverse proxy at the time. Here is the thread discussing that experience:

If you set up the icloud account with your new VM, it may not be an approved imessage account yet. Check here and see if this helps:

Looks like @grtgbln added the cal.com template to their repository back in September. It is available on community apps if anyone has been waiting for it to appear again. The XML template is here: https://github.com/nwithan8/unraid_templates/blob/main/templates/cal_com.xml However, you can just search for cal.com on CA, and it should be visible.

I upgraded to 6.12.13, after everything was back up and running. I went to the VM (same install I made on 6.12.10) and changed the cores and ram, click update, went back to macinabox and started the container again, once I got the successful message I ran the Sonoma VM and it is working without the "Guest has not initialized the display yet" error. So whatever is changed in the latest update of unRaid, there is a bug that is causing this problem for some of us. If you haven't upgraded to 6.12.13, this will hopefully fix the issue for you.

I am seeing a couple people saying version 6.12.10 may be the issue. I usually wait until 30 days after a release before upgrading but got distracted when this was released. Doing my upgrade to 6.12.13 to see if that allows this to start working again.

Yep, right now this is not letting us change any VM settings without ruining the install. At this point, I'd just wait until a solution is posted.

Don't change it if you want to be able to run it without some other fix. I did this as well, let it install using default cores and ram. Once you try to change it, you'll get the error again. Any time you edit the VM settings, you have to rerun macinbox container and I think that's where this is going sideways for us. I'm guessing this is happening to a bunch of users, so hopefully he can help us figure out a solution. Waited this long for Sonoma, I'm happy to wait a little longer:)

I did this when I first had difficulty getting the install to run. I'm on unRaid 6.12.10, the installation of Sonoma went fine, but I left the settings as default (4gb of ram, 2 cores). After the install completed, I went to change the icon, ram and cores, and now I keep getting the "Guest has not initialized the display yet" even when I try to change it back to the default settings. I re-ran the macinbox container (probably not a good idea) so if I have to redo from scratch no biggie. I guess I want to know what I should do to avoid getting that error in VNC but still get everything to run. Let me know if you need additional details, thanks @SpaceInvaderOne

@SpaceInvaderOne has not posted any updates here, what video are you referring to?

Just in case this was not explained, you would need to edit your vaultwarden (or in my case bitwardenrs) subdomain conf if you wanted to remove admin access. Open the conf file and find the section that begins with location ~ (/bitwarden)?/admin { further down you should see the following lines: # include /config/nginx/proxy.conf; # include /config/nginx/resolver.conf; # set $upstream_app CONTAINER_NAME; # set $upstream_port PORTNUMBER; # set $upstream_proto http; # proxy_pass $upstream_proto://$upstream_app:$upstream_port; As you see, I added '#' at the beginning of the line, which disables them when you save. Do not put '#' at the beginning for the location or at the end with the closing '}' The curly brackets need to exist, otherwise will enable access again. Save the conf file and restart the swag container. You should still have local access using the ipaddress:port/admin and it should return a 404 error if you try access it with the subdomain.

You can search around for guidance, but it can be installed with some effort, see previous post on this topic:

I agree it's easier when money isn't a factor, but it's another hardware set to maintain and use power. I don't know what you are inferring about "safer for your Apple ID, " as using an Apple ID on a VM is not inherently dangerous. People may not understand the cause when something goes wrong, but no need to jump to conclusions that apple is going to blacklist an account when it's never happened. Temporary difficulties and lock outs occur, but I have yet to hear about a permanent ban from a user. Finding a bargain on a used Mac mini like the 2018 version that allows a person to upgrade the RAM and run the latest macOS smoothly will be less work than getting this working on the server. Some of us like to tinker, and others just want it to work without hassle. To each their own:)

@plantsandbinary I'm sorry this didn't end up working for you. I think the difficulty is troubleshooting without a control device. If you have a friend who can sign in with their credentials on the MacVM and they can communicate, then you can rule out the VM as being the issue. If you can sign in on someone's apple device that works for them, you will know if it's your appleid that is't working. I still believe since you can message yourself that the appleid has been activated and isn't blocked from apple, but I can be completely wrong. I wouldn't suggest a wipe and fresh install of the mac os before troubleshooting further, but it's all I can think of to help. Again, sorry this was such a waste of time, but if you manage to figure out a fix in the future, feel free to share an update. Good luck!

Speaking for myself, I am running a BigSur MacVM in unRaid and used the Macinabox container to set it up by following @SpaceInvaderOne's tutorial video here: I have not made any modifications or upgrades to my install, so I followed Ed's instructions exactly as he explains them.

If the bluebubbles is showing imessage connected and all the services are green, it sounds like you are setup on apple's and bluebubble's side for this to work. It seems like something is wrong in the VM configuration or something else causing the messages not to work. I don't think it's a DNS issue because the test message wouldn't work. How about a password reset to see if that does anything? Another possibility is just disabling apple contacts and try messaging someone without selecting them. It's frustrating because it sounds like you have it working, but it just won't work...

I can assure you there is no ban on Apple servers if you can sign into your account. Try going to https://appleid.apple.com/account/manage and see if everything looks good in the settings and the sign in and security section. You can try signing out of your appleID and also sign out within imessage and then try logging in to each separately to see if it's a login error possibly (just guessing now). If messaging yourself is working, then it might just be as simple as restarting the system. I am sorry I don't know of other ways to fix this for you. The old "turning it off and on again" option is all I have left to offer...

Yes, I am saying you can absolutely message your friends on imessage with this set up, phone number and all. The private API is not necessary for it to work, it just adds additional fun features likes reactions, typing indicators, etc. But it should work on the macVM without additional steps. If the contact you are entering is switching from imessage to SMS forwarding, then it might be a contact detail issue. I don't sync my phone contacts with bluebubbles or imessage as I want to keep the contact list segregated from non-apple users. Try typing in their phone number instead of just clicking on their contact name, or remove all contacts on the macVM and try adding one person at a time to message and see if it works that way. It's not hard to get this all working properly once you figure out a system that works for you. I hope that helps and good luck!

I use bluebubbles with family and friends and nobody has any issue having conversations with me using my appleID instead of my phone number. Once you have a starter conversation, they just need to message back and forth with you in that message instead of your phone number. It will work for group messages too, as long as everyone is imessage/iphone user. To be clear, you can message anyone at their imessage phone number or appleID, you cannot message non-apple phone numbers from your appleID imessage account. This is strictly to communicate with apple people in their walled garden of imessage. It should work for you with that understanding, so if it is still an issue and you are getting red delivery errors, then I may have exceeded my abilities to help you:)

You can only use your appleid email to communicate with imessage or bluebubbles with other imessage accounts. You cannot use your phone number unless it is registered with an iPhone, and there are some workarounds that will let you stay on a non-apple phone to keep it registered, but that's not what we are doing here. So yes, the only way to reach you in imessage is the email address showing in the preferences, they cannot message you through your number, it will just show up as a regular text to you. They need to send an imessage to your email account for it to work. And when it is sent from you, it's coming from your email and not your phone number. I hope that is clear in case there was any confusion why your contacts were sending it to your phone number instead. Your phone number associated with your account will only be for verification codes and does not connect to imessage on the VM. I think this is difficult because you don't have a second device to test this with, but it sounds like the imessage is working for you. See if you can send a test message to yourself at your applid email from the imessage account. If you do not see any delivery errors, then I am sure the imessage is working properly.