Glenn
-
Posts
33 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Glenn
-
-
my motherboard has two nics
-
5 hours ago, ijuarez said:
very odd it looks like your containers do not have the host ip 192.168.7.60, also is there a reason why you chose to have most of your containers in host mode instead of bridge mode.
Care to share your network settings page.
I haven't really learned the ins and outs of the modes yet, so I just went off of what the guides i was using had.
-
2 hours ago, ijuarez said:
No, that's is just letting you the LE container is working, you need to access your server via it's new port 192.168.7.60: XXX
Sent from my BND-L34 using Tapatalk
I can access the server by putting :8080 at the end of my ip. But I can’t access the dockers. That’s the message I get when I click webui on any of my dockers except plex
-
I assume this error when trying to accesd docker gui is because of letsencrypt
-
nevermind. i guess i also had to change not just port 80 in identification but also 443??? because i changed 443 to 4443 and now it starts.
i cant access my other dockers from the webui after changing the id though. do i have to adjust config files for those programs?
-
the internal ip of my server is 192.168.7.60.
i use an eero mesh wifi with a netgear prosafe switch if that is what you mean by my network setup.
also tried removing letsencrypt and then reinstalling. this is what i get:
-
-
15 minutes ago, ijuarez said:
Did you intentionally blur the ips on the containers that are not on the proxy net,?
Sent from my BND-L34 using Tapatalk
no.
and after rebooting my server i get an execution error whe trying to start the docker
-
Just now, ijuarez said:
I suggest you head over to youtube and search for spaceinvader one he is member if this forums and has produced some great how to's
Sent from my BND-L34 using Tapatalk
i have watched a ton of his videos (multiple times). i guess im just inept
-
4 hours ago, Squid said:
Settings - Identification - Management Access
after doing this i cant open my containers through webui (except plex). am i missing another setting? i did get the server ready under the letsencrypt log though.
-
Can you explain how to remap port 80? I have searched and seen several different things about changing a go file and changing a file on the flash drive. But nothing was very straight forward. ie, step 1,2,3 etc.
-
4 minutes ago, ijuarez said:
Your ISP is probably blocking port 80
Sent from my BND-L34 using Tapatalk
so how do i fix it??
-
i need some assistance with letsencypt. i keep getting a binding error for port 80. Im also not very smart, yall will have to dumb it down barney style for me.
-
i think my ass got hacked after trying to open up my server for remote acces through tonido..........
-
if i login through microsoft edge i see an error 401 authorization required and below that it says nginx. trying to login through chrome just brings me back to the login screen for my credentials
-
for some reason after rebooting my server i cannot login. i have never had problems before. i can still see all of my folders through the network but i cant acces the gui login even though i DO put in the correct username and password. WTF??????? please help
-
Thanks. And I don’t know if your username correlates, but I drink Johnnie Red everyday. and I owe ya one
-
I was using my spare system running windows with Plex and locally sharing folders (with issues).
I sure am glad I decided to back up my stuff and then switch to unraid. I would have never known that drive was failing/failed.
Also I guess that disk was my problem because now parity is syncing quite nicely now. It’s at 11 hours rather than 100 DAYS. Lol.
Thanks to all who contributed. I guess now I can go from trial to purchasing.
-
by the way.... i really appreciate your help and patience. thank you
-
did you look at the last diag report i posted?
it says : 00:1f.2 SATA controller [0106]: Intel Corporation 6 Series/C200 Series Chipset Family 6 port Desktop SATA AHCI Controller [8086:1c02] (rev 05)
Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:844d]
Kernel driver in use: ahci
Kernel modules: ahciis that not right?
-
if i reflash my bios i just want to know how to check to see if it is working correctly
-
how do i navigate to my diagnostics log to see where you are seeing that?
-
would you mind explaining how you come to that conclusion?
also is there a "guide" anywhere explaining how to sort through the diagnostics log and what to look for?
after all of my recent changes i reran my diagnostics. my current info is attached.
-
ok.
also, i rechecked my bios settings. it says its ahci. the only thing under pch is high precision timer. all other sata options are under the sata tab. i looked in every menu option for additional sata settings.
[Support] Linuxserver.io - Nextcloud
in Docker Containers
Posted · Edited by Glenn
Hi, i have letsencrypt running, server ready. When i click on webui under docker i get redirected to my subdomain, but it times out. I get this:
my nextcloud config is:
<?php
$CONFIG = array (
'instanceid' => 'oc2r526nrw27',
'passwordsalt' => 'jahrU20+WU1udvy0TZpnKPrZhRnNC2',
'secret' => 'l4iHAz1Fz0pCfZ44QhzzqGwy9gbpKrc8DEsz2uxjZer/+85E',
'trusted_domains' =>
array (
0 => '192.168.7.60:444',
1 => 'xxx.duckdns.org',
),
'datadirectory' => '/data',
'dbtype' => 'mysql',
'version' => '14.0.0.19',
'trusted_proxies' => ['letsencrypt'],
'overwrite.cli.url' => 'https://xxx.duckdns.org',
'overwritehost' => 'xxx.duckdns.org',
'overwriteprotocol' => 'https',
'dbname' => 'nextcloud',
'dbhost' => '192.168.7.60',
'dbport' => '',
'dbtableprefix' => 'oc_',
'mysql.utf8mb4' => true,
'dbuser' => 'glenn',
'dbpassword' => 'Titan001',
'installed' => true,
);
my letsencrypt nextcloud.subdomain.conf file looks like this:
# make sure that your dns has a cname set for nextcloud
# assuming this container is called "letsencrypt", edit your nextcloud container's config
# located at /config/www/nextcloud/config/config.php and add the following lines before the ");":
# 'trusted_proxies' => ['letsencrypt'],
# 'overwrite.cli.url' => 'https://nextcloud.your-domain.com/',
# 'overwritehost' => 'nextcloud.your-domain.com',
# 'overwriteprotocol' => 'https',
#
# Also don't forget to add your domain name to the trusted domains array. It should look somewhat like this:
# array (
# 0 => '192.168.0.1:444', # This line may look different on your setup, don't modify it.
# 1 => 'nextcloud.your-domain.com',
# ),
server {
listen 443 ssl;
server_name nextcloud.*;
include /config/nginx/ssl.conf;
client_max_body_size 0;
location / {
include /config/nginx/proxy.conf;
resolver 127.0.0.11 valid=30s;
set $upstream_nextcloud nextcloud;
proxy_max_temp_file_size 2048m;
proxy_pass https://$upstream_nextcloud:443;
}
}