Good afternoon dear supports, I am trying to understand the infrastructure of aaPanel and the built-in OpenLiteSpeed. I am limited in my choice of webservers ( only OLS ) that why I can`t switch to ngnix. The essence of the question is: Is it possible to run my own docker container image from the code on GitHub? Is it possible to restrict this docker to interact with my WordPress site via API exclusively locally, so that it is not possible to access this docker container from the outside world via IP? The Docker container itself must connect to the API of another, global site(not loca, not mine - public api) in order to receive currency exchange rate data. Essentially, the container is needed as a microservice that will act as a calculator and send data to my WordPress page via API, receiving and returning data.

WordPress site via OpenLiteSpeed + docker images

aaP_alexsandr.true

Good afternoon dear supports, I am trying to understand the infrastructure of aaPanel and the built-in OpenLiteSpeed.

I am limited in my choice of webservers ( only OLS ) that why I can`t switch to ngnix.

The essence of the question is:

Is it possible to run my own docker container image from the code on GitHub?
Is it possible to restrict this docker to interact with my WordPress site via API exclusively locally, so that it is not possible to access this docker container from the outside world via IP?
The Docker container itself must connect to the API of another, global site(not loca, not mine - public api) in order to receive currency exchange rate data.

Essentially, the container is needed as a microservice that will act as a calculator and send data to my WordPress page via API, receiving and returning data.

aaPanel_Kern

Hello,
You can provide services to customers through reverse proxy

aaP_minerslol44

Interesting setup you’re trying to build. Running a microservice inside Docker that talks only to your WordPress site sounds clean and secure in theory — just needs careful network handling.

You might want to look into Docker’s internal bridge network; it can allow your container to communicate with the site locally without exposing it to the public. From there, the external API connection should still function properly as long as outbound requests are permitted.

Not an exact fix, but that’s probably the direction worth checking.