-
I want to set up a DNS server to route internal traffic directly to Nextcloud on my Ubuntu VM on Truenas so the data doesn't have to go out and then back in. I'm not used to this kind of set-up and can't think of what to do. Can someone point me in the right direction, please? the internal IP on ports 80 and 443 both get refused. Do I adjust the config file for Nextcloud or Apache? If Apache, how do I get to the configuration within this docker image? Sorry, I've only ever run on bare metal before and am still new to this. Awesome, AWESOME work by the way. This takes so much headache out of Talk and the HPB for people like me. I only wish I was smart enough to have it run directly on my Truenas Scale rather than in an Ubuntu VM on it. |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 3 replies
-
Hello, I don't unerstand at which point it fails. Can you please add the exact steps you took here and maybe also add a screenshot? Thanks! |
Beta Was this translation helpful? Give feedback.
-
Thanks for your reply.
What details would you like? The Nextcloud config? I have not really
touched anything in the docker as it worked so well out of the box.
The server is at 192.168.2.11 and if I try that address in a browser with
http or Https, 80 or 443, the server refuses. The 8080 port for the aio
interface works but says to go through the settings which I believe is
normal.
I feel like it's a trusted address issue in Apache or NC? I entered my
external domain name when I set up the aio image and that works perfectly.
I can access that from inside and outside the network.
I just can't access Nextcloud with the IP address over the LAN.
I only want to be able to make use of my 2.5g LAN when inside the network.
…On Thu, May 12, 2022, 08:50 Simon L. ***@***.***> wrote:
Hello, I don't unerstand at which point it fails. Can you please add the
exact steps you took here and maybe also add a screenshot?
Thanks!
—
Reply to this email directly, view it on GitHub
<#618 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWWIX7X7BYFVVPBZFVU2HYTVJRBVTANCNFSM5VWNREVA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Https://192.168.2.11:443 returns "This site can't provide a secure
connection"
Http://192.168.2.11:80 returns "connection refused"
…On Thu, May 12, 2022, 09:00 Dale Berry ***@***.***> wrote:
Thanks for your reply.
What details would you like? The Nextcloud config? I have not really
touched anything in the docker as it worked so well out of the box.
The server is at 192.168.2.11 and if I try that address in a browser with
http or Https, 80 or 443, the server refuses. The 8080 port for the aio
interface works but says to go through the settings which I believe is
normal.
I feel like it's a trusted address issue in Apache or NC? I entered my
external domain name when I set up the aio image and that works perfectly.
I can access that from inside and outside the network.
I just can't access Nextcloud with the IP address over the LAN.
I only want to be able to make use of my 2.5g LAN when inside the network.
On Thu, May 12, 2022, 08:50 Simon L. ***@***.***> wrote:
> Hello, I don't unerstand at which point it fails. Can you please add the
> exact steps you took here and maybe also add a screenshot?
>
> Thanks!
>
> —
> Reply to this email directly, view it on GitHub
> <#618 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AWWIX7X7BYFVVPBZFVU2HYTVJRBVTANCNFSM5VWNREVA>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
Beta Was this translation helpful? Give feedback.
-
So to simplify my issue: I think when you set the domain name on the aio setup, it enables that and disables the internal address somewhere. cloud.example.com becomes the only way to access Nextcloud. Your work has made it far more accessible to me, but I just have this little hiccup. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
You need to use your domain |
Beta Was this translation helpful? Give feedback.
-
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:"Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
***@***.*** Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
code
{mso-style-priority:99;
font-family:"Courier New";}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
-->Aaaaah I see.Yes, that is what I want to do. I was just testing that the local lan would work before installing and setting up PiHole. When I saw that it wouldn’t work in the browser, I assumed it wouldn’t work with PiHole.I’ll give it a try. Thanks again. Sent from Mail for Windows From: Simon L.Sent: 12 May 2022 14:47To: nextcloud/all-in-oneCc: DaleJP; AuthorSubject: Re: [nextcloud/all-in-one] Internal LAN access - I think I'm being dumb (Discussion #618) You need to use your domain cloud.***************.jp to connect to your Nextcloud even in your LAN. However what you can do in order to make access faster is install a local dns server like a pihole that automatically points to the local ip-address of your Nextcloud when accessing your domain inside your LAN.—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
You need to use your domain
cloud.***************.jp
to connect to your Nextcloud even in your LAN. However what you can do in order to make access faster is install a local dns server like a pihole that automatically points to the local ip-address of your Nextcloud when accessing your domain inside your LAN.