this post was submitted on 08 Nov 2023
2 points (100.0% liked)
Self-Hosted Main
21 readers
1 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
For Example
- Service: Dropbox - Alternative: Nextcloud
- Service: Google Reader - Alternative: Tiny Tiny RSS
- Service: Blogger - Alternative: WordPress
We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.
Useful Lists
- Awesome-Selfhosted List of Software
- Awesome-Sysadmin List of Software
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You have to set the docker container name as the destination, not the host IP.
Test everything from the beginning.
# check your FQDN is set up correctly.
$ nslookup 1.1.1.1
$ nslookup 8.8.8.8
# Test your web host from out of the docker host.
$ curl -v http://your_fqdn
# test your web host on the host machine.
$ curl -v -H "Host: your_fqdn" http://localhost
# check if your port is exposed if you map it.
docker ps | grep
# check if your mapped port is listening on the docker host
netstat -tlnp | grep
#check if your container is reachable by NPM.
docker exec -it bash
[root@docker-278f29455e29:/app]# apt update && apt install netcat
[root@docker-278f29455e29:/app]# nc -zv
if NPM reaches docker, you're OK.
There are many things you have to check more, for example, NPM and your destination container should be in the same docker network.
# docker inspect | grep NetworkID
# docker inspect | grep NetworkID
They should be equal.
etc. etc.