Cockpit blanc page

Bug
1

Blanc page on cockpit…I have reeinstalled it… But nothing… Deciding to change into pfsense, and rest with a only nethserver ad fileserver on it.final objective pfsense - - - - nginx vm—apache webservers with subdomains and certbot

2

Maybe related:

1 Like
3

Switched to English and solved, but I will migrate to pfsense…

4

Can we know why? Maybe we can help you :wink:

1 Like
5

What I want more stability and also because at work. I am learning to put pfsense and nginx reverse proxy for internal apache webservers…so I need a last stand with nethserver, to achieve my goal on nginx reverse proxy, with my pi hole as dns resolver… On pfsense we have clearly that configured on job forwarding to nginx reverse… I saw that is easyer with nethserver, but it didn’t work… For instance…
Finally my goal, is to put the nginx container working on proxmox, using pi hole as my dns resolver(done). On nethserver my first dns is pi hole the second is nethserver itself. Also the objective, is to forward the request to nginx reverse proxy container, to have my web app servers being attainable from outside with ssl cert bot, which I am stuck on the configs…

6

You make reconsider my opinion because I have felt in love with nethserver a long time ago …

7

just for my information did you install pihole manually ?

8

did you test traeffic ?

It is a docker proxy container for container

9

Yes manually in proxmox vm debian github script pihole

10

No I am not so confortable with but does not seams hard to implement… To watch the network flow passing I assume?

11

Screenshot_20201012_161129_com.android.chrome
Screenshot_20201012_161129_com.android.chrome1080×2312 334 KB
inside with the domain name pi hole has nethserver ip pointed to this subdomain from outside nothing is the pi hole or nethserver blocking… I have firewall nethserver active, idS also too
From outside I will test traefik
Screenshot_20201012_160708_com.android.chrome
Screenshot_20201012_160708_com.android.chrome1080×2312 180 KB

12

Holly smoke I Did it yeahhhhhhhhh​:muscle::grin::slight_smile::grin::slight_smile:
Firewall port forwarding + nethserver nginx proxy gui + dns on nethserver + tric between the port on nextcloud 444 /nextcloud/config/config.php internal on nextcloud container trusted domain:444, now I have dokuwiki on 443

3 Likes
13

Only misses the ssl certificate for nethserver do you know how can I achieve this with certbot or an ssl buyed one… I saw there’s caveats on it to avoid screwing the nethserver webgui