Thanks for this video. Still waiting for the follow-up you promised to see how you installed other containers and protected them with Nginx Proxy Manager. Thanks again!
I have just finished following this video and have everything working. I would like to get Lets Encrypt working so I am looking forward for your next video in this series. Thank You!
Al ejecutar este comando yum-config-manager --enable ol7_optional_latest, me sale ese Error: No matching repo to modify: ol7_optional_latest. how do I solve it?
If you have created an ingress rule to allow traffic on port 9443, it is possible that the issue is with the SSL certificate. By default, Portainer uses a self-signed certificate, which may not be trusted by your browser. To resolve this issue, you can either add the self-signed certificate to your browser's trusted certificates, or you can use a trusted SSL certificate. Here are the steps to use a trusted SSL certificate with Portainer: Obtain a trusted SSL certificate for your domain. You can obtain a free SSL certificate from Let's Encrypt using a tool like Certbot. Copy the SSL certificate and private key to your server. Update the docker-compose.yml file for Portainer to use the SSL certificate and private key. Add the following lines under the portainer service: ports: - "9443:9443" volumes: - /path/to/cert.pem:/cert.pem - /path/to/privkey.pem:/privkey.pem environment: - TZ=America/New_York - SSL_CERT_FILE=/cert.pem - SSL_KEY_FILE=/privkey.pem Replace /path/to/cert.pem and /path/to/privkey.pem with the paths to your SSL certificate and private key files. Run docker-compose up -d to start Portainer with SSL enabled. Once you have updated the docker-compose.yml file and restarted Portainer, you should be able to access Portainer using HTTPS on port 9443.
Great video! I have a question, on the second step, yum-config-manager --enable ol7_optional_latest i get an error: No matching repo to modify: ol7_optional_latest Any ideas?? Tks.
The error message "No matching repo to modify: ol7_optional_latest" suggests that the repository configuration for the Oracle Linux 7 optional latest repository may not be available or properly configured on your system. You can try to check if the ol7_optional_latest repository is enabled on your system by running the following command: yum repolist enabled | grep ol7_optional_latest If it returns an empty output, it means that the repository is not enabled on your system. In this case, you can try to enable it by running the following command: yum-config-manager --enable ol7_optional This will enable the Oracle Linux 7 optional repository, which includes the latest packages for Oracle Linux 7. After enabling the repository, you can run the yum-config-manager --enable ol7_optional_latest command again to enable the latest packages in the repository. If you still encounter issues, you can try to check if the repository configuration file for ol7_optional_latest exists in /etc/yum.repos.d/ directory. If it does not exist, you may need to create it manually.
Hi, very good video. I have moved on and created a host to be able to access Nginx from the internet. I have my subdomain pointing to oracle. Till I keep port 81 open in Oracle, all works fine. If I close port 81 in the Oracle Ingress Rules, I cant access it anymore. You mentioned in this video that is than possible to delete the port 81. How? More over, I am familiar with Nginx in my own network and have many Hosts configured, but I am unable to redirect to a service using Nginx on Oracle. Can you show us an example please?
Hello, You can direct the port 81 using proxy manger. Than you can go at the firewall on the oracle cloud and remove port 81. In this way you are still able to use your Nginx but the only open port will be the port 80 for http and port 443 for https. Regarding second question, it will be in one of my next videos. Meanwhile, here's an example of how you can use Nginx on Oracle Cloud to redirect traffic to a service: Let's say you have a service running in a Docker container on port 8080, and you want to access it using a subdomain, "example.domain.com". 1. First, create a new configuration file for the Nginx server block by running: sudo nano /etc/nginx/sites-available/example.domain.com.conf 2. Then, add the following contents to the file: server { listen 80; listen [::]:80; server_name example.domain.com; location / { proxy_pass localhost:8080; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; } } 3. Save and close the file. 4. Next, enable the new configuration file by creating a symbolic link to it in the sites-enabled directory: sudo ln -s /etc/nginx/sites-available/example.domain.com.conf /etc/nginx/sites-enabled/ 5. Then, test the configuration and reload Nginx by running: sudo nginx -t sudo systemctl reload nginx Now, when you visit "example.domain.com" in your web browser, Nginx will redirect traffic to the service running on port 8080. Note: Make sure you have opened the necessary ports in your Oracle Cloud firewall rules to allow traffic to reach the Nginx server.
@@sauberlab-uk Hi, thanks for your reply. Now, thats the thing, when I delete port 81 from the ingress rules, I loose the access to Nginx. and I am forwarding the request to port 81. And I also am able to create a letsencrypt. But if port 81 is gone from the ingress rules, I dont access it anymore. Is it possible that the IP to forward to is the tricky part? I must use the cloud IP to be able to access Nginx after port forwarding within Nginx (yet with ingress rules port 81 open). In relation to the second question, I guess I will pick it up after I am able to access Nginx. Any extra suggestions are welcome Thanks
@@donglobal feel like we need a part 2 video about going in depth on how to access your containers within the bum externally. From front end, backend, and even the database
Sure, meanwhile, I can provide some more information on ingress rules and how to troubleshoot issues with accessing containers outside of your VM on Oracle Cloud. Ingress rules allow incoming traffic to your virtual machine (VM) from a specific port or IP address. In order to access containers outside of your VM, you need to set up ingress rules that allow traffic to flow from the internet to your VM. Here are some steps to troubleshoot issues with accessing containers outside of your VM: Check that the ingress rule is set up correctly. Make sure that the ingress rule allows traffic to the specific port that your container is running on. You can check this by running sudo iptables -L -n on your VM and looking for the port that your container is running on. Check that your container is listening on the correct port. You can check this by running sudo docker ps to list your running containers, and then running sudo docker inspect [container_id] to see the container's details, including the port it is listening on. Check that your container's network settings are correct. By default, Docker creates a network for your container, and the container is assigned an IP address on that network. You need to make sure that the container is configured to use the network that you want it to be accessible on, and that the network settings are configured correctly. You can check this by running sudo docker network ls to list the available networks, and then running sudo docker inspect [container_id] to see the container's network settings. Check that your container's firewall settings are correct. If your container has a firewall installed, make sure that it allows traffic to the port that your container is running on. You can check this by running sudo docker exec -it [container_id] bash to open a shell in the container, and then running sudo iptables -L -n to list the container's firewall rules. If you've checked all of these steps and you're still having issues accessing your container outside of your VM, it may be worth checking your Oracle Cloud network settings and security rules to make sure that traffic is allowed to flow from the internet to your VM. I hope this helps! Let me know if you have any other questions.
I tried to use this same method, opening port 2375 on ingress rules, to be able to access with Portainer on my own server to the docker api on the Oracle VM but still I cant acess to it. What I could be doing wrong?
Sorry Guille, But i did not get what you intend to do. Could you please explain better? if I understand correct, you want to do a cluster between oracle cloud and your server. Could you please tell me if i get it correct?
@@sauberlab-uk I have Portainer installed on one of my home servers, and I use that container to access the docker API in other machines, not to use it as cluster, but just to manage the different docker machines. I was trying to do the same to access to the docker API on the Oracle VM, but can't reach it even if I open the port on the ingress rules. I had to also open the port on the iptable on the VM, after that it worked great.
@@guillepunx I understand what you mean but please tell me you figured it out?? I have another container i want to access and added an ingress rule but cant connect still. I hope youre still alive in this world bro I need to figure this shit out
Hello, the only method that I know is do the log in on the nextcloud and create a new account Than delete the stand NCP account. The other method is going to the SQL, but I`m not confident about this. Could you please tell me the issue that you have? In this way I can see if I`m able to help you.
Yes, this guide should work on Oracle Ampere instances as well, as long as the instance is running Oracle Linux 7.9 or later. The steps for installing Docker, Portainer, and NGINX Proxy Manager should be the same regardless of the instance type.
