How domains in hestiaCP docker can go out to the real world?

For those who find the easy hestiaCP docker to use (still has issue)

I’ve tried this one. It’s work for me follow it’s instruction.


edit


I can’t restore the backup because of the permission problem.

docker exec hestiacp /usr/local/hestia/bin/v-restore-user test test.2025-12-17_03-23-44.tar

– WEB –
2025-12-22 14:08:32 test.test
mkdir: cannot create directory ‘/home/test’: Permission denied

… all about permission …

  • Even I pre-create the user, the problem still going on.
  • This does not work as well: docker exec -u root hestiacp /usr/local/hestia/bin/v-restore-user test test.2025-12-17_03-23-44.tar

I think it’s working now by copying v-restore-user’s content and put in the docker’s bash terminal. I just don’t know how to test :expressionless_face: How “test.test” domain and other domains in hestiaCP docker can go out to the real world?

It is v1.8.11, very old, and not suggested. Still for people, it maybe a start.

2 Likes