Nick Howitt wrote:
I've just tried VLC and it sees something the server Local Network > Universal Plug'n'Play, does not show anything more than the server on a single line, waits a bit and crashed, so I cant use it either! It works with my TV.
For me, VLC for macOS never sees the server. When I look into its log, I find lines of the following:
I don't know that address in the log or where it comes from (my server is at 192.168.0.1). I tried to trace the source of that IP but could not find it any where in the VLC nor in the Plex Resources/Profiles files.
Nick Howitt wrote:
Why not just install the plex repo and do a yum update...... (I keep mine disabled so I can update when I want).
I did that, but it only fetches public releases not "pass" ones. It also broke for some reason and I didn't bother fixing it. The plex gives me the link whenever a pass (beta!) version is released and I just pass it to yum. I also need to delete the rpms accumulating in /tmp folder from time to time.
Thank you Nick.
When Oracle acquired MySQL, almost everyone thought then the days for MySQL being open and free are about to end. Many jumped of the sinking ship (as they thought) and went to the nearest open and free compatible database engine. But all of that was in the past, and MySQL is still open and free.
For me, I actually like percona since it is fully compatible with mysql and also offers free thread pooling.
Although the MySQL app is listed in the marketplace, it is not actually available for new clearOS systems. It is clear that MySQL app has been replaced with MariaDB app.
I'm not sure why that happened, but MariaDB should not replace MySQL! These two database engines are not compatible with each other. Yes, MariaDB used to be a one-way drop-in replacement for MySQL, but that has changed after version 5.5, which clearOS uses by default.
Nowadays, MariaDB lags behind MySQL in many new areas, such as GIS and JSON support and Memory engine. There are big chances now that apps developed for one engine would not run on another.
This is a call for clearOS to reconsider using MySQL again or offer a true compatible open-source engine.
So Lets install a container. I want to start with Transmission. I've chosen the Transmission Docker container of Timhaak.
Let's pull the Docker image
We can check if the image is downloaded with:
So now let's see the command how to start the container:
We run the container in deamon mode "-d" You see some mappings they begin with "-v" The directories inside the container are mapped to outside flexshares. Of course you have to create the flexshares. Also you have to create a directory appdata so the config of transmission is stored outside of the container. Then we have some port mappings beginning with "-p". We set the user and password with "-e".
Let's run the container!
Now check with:
You can access the container with the ip-address of your ClearOS server and port number "9091".
Install Docker on ClearOS 7.x
***Important please try this first in a VM***
Docker needs at least kernel version:
My VM of ClearOS 7.2 Community has:
Make sure ClearOS is updated
Copy past the followingl:
Packages being installed
Verify that Docker is installed and running.
Start Docker at boot
Run/install "hello-world" container (Docker first search if the hello-world is install. If not it download and installs the container.
You can also check if the docker image has downloaded with:
You can also check for running containers with:
You see that NZBGet is running on my ClearOS server.
I needed to receive emails for two different domains. ClearOS is very clear on not allowing virtual domains hosting for emails, as explained on this document: Does ClearOS Support Multiple Virtual Mail Domains?
My requirements are:
1. Messages sent to addresses on the two domains must be kept separated.
2. Replies must be sent from the original receiving domain, not from the clearOS main mail domain.
The clearOS can receive emails for different domains. Additional domains can be entered in Server -> Messaging -> SMTP Server -> Destination Domains. The server keeps mails sent to all domains in one account. For example, message sent to user1@main_domain.com and to user1@x_domain.com are all kept in user1@main_domain.com account. So, user1@x_domain.com is just an alias for user1@main_domain.com.
Based on these facts, I had 3 options:
1. Install a virtual machine on KVM/Kimachi for hosting email service
2. Outsource email service
3. Find a way to use clearOS and meet the requirements at the same time.
The first option would complicate my network, as I then need to manage two or competing mail servers at the same network (clearos and the VM one).
The second option costs money and since the domains I host are not commercial, I don't want to pay for their emails.
This left me with the third option! Fortunately, I was able to do it and meet the requirements as explained in the following:
1. Configure clearOS to rely outgoing messages using a third party. I used sparkpostmail and added the required settings in /etc/postfix/main.cf:
2. Accordingly, configure the two domains' DNS hosting records at the registrar page.
3. The tricky part was to setup my email client (I'm using macOS Mail) to separately receive messages for the two domains. So, messages for user1@main_domain.com go to its own account and messages for user1@x_domain.com go to its own accounts. This can be achieved my creating two POP accounts, then adding rules to each one as follows:
- If an incoming message is for account "main_domain.com" and recipients addresses contain "x_domain.com", then delete it. (make sure the POP account is configured not to delete messages on the server)
- If an incoming message is for account "x_domain.com" and recipients addresses contain "main_domain.com", then delete email. (make sure the POP account is configured not to delete messages on the server)
This trick keeps emails mixed on the server of course, but on the client, they are separated as if they come from two different accounts.
One limitation of this method though is when a message is sent to both domains. Then the client would not receive it in either account. In my situation this unlikely to happen as the two domains are unrelated to each other in the real world.