1 |
Hi there, |
2 |
|
3 |
The problem has a rather simple cause and also a simple solution: |
4 |
|
5 |
Nextcloud expects a working DNS server for resolving its own app server, |
6 |
*then* it is using the proxy to access it. |
7 |
|
8 |
After configuring a DNS proxy in my DMZ and ensuring that /etc/resolv.conf on |
9 |
the nextcloud instance is correctly pointing to it, it suddenly works :-) |
10 |
|
11 |
Alex |
12 |
|
13 |
|
14 |
On Sonntag, 19. Februar 2023, 13:17:41 CET Alexander Puchmayr wrote: |
15 |
> Hi there, |
16 |
> |
17 |
> I'm trying to setup a nextcloud instance inside a DMZ that has no direct |
18 |
> connection to the outside world, only via proxy. The proxy itself is working |
19 |
> fine, but I fail to configure nextcloud to actually use this proxy. |
20 |
> |
21 |
> According to the docs, I tried setting the proxy field in config/config.php, |
22 |
> i.e. |
23 |
> |
24 |
> <?php |
25 |
> $CONFIG = array ( |
26 |
> ... |
27 |
> 'proxy' => '10.46.1.109:3128', |
28 |
> 'proxyuserpwd' => '', |
29 |
> ... |
30 |
> ); |
31 |
> |
32 |
> But this setting seems to be ignored, tcpdump does not show any connection |
33 |
> attempt to that ip and nextcloud complains that it cannot connect to the |
34 |
> internet. |
35 |
> |
36 |
> In another forum I found that in |
37 |
> /etc/apache2/vhosts.d/10_nextcloud_vhosts.conf, environment variables like |
38 |
> HTTP_PROXY and HTTPS_PROXY may be set, i.e. |
39 |
> |
40 |
> <VirtualHost *:80> |
41 |
> ... |
42 |
> SetEnv HTTP_PROXY 10.46.1.109:3128 |
43 |
> SetEnv HTTPS_PROXY 10.46.1.109:3128 |
44 |
> ... |
45 |
> </VirtualHost> |
46 |
> |
47 |
> But this also does not seem to work. |
48 |
> |
49 |
> Any other ideas? |
50 |
> |
51 |
> Thanks |
52 |
> Alex |