The initial setup doesn't require the SWAG part.
That is why port 450:443 is there.
After having it setup locally, then it's time to make the changes for remote access.
The initial setup doesn't require the SWAG part.
That is why port 450:443 is there.
After having it setup locally, then it's time to make the changes for remote access.
The initial setup doesn't require the SWAG part.
That is why port 450:443 is there.
After having it setup locally, then it's time to make the changes for remote access.
That's how I always do it.. but I think maacom's tutorial is a little different.
The only thing about setting up Nextcloud locally is that when you introduce Swag you have to remember to set the reverse proxy .conf file to include the local AND the remote address in the trusted domains array. Example here. I couldn’t figure why I could access remotely but not locally until I saw this little rid-bit. You could access locally before setting up Swag. Why not after? Duh, me!
Anyone know an easy way of updating the Linuxserver docker version of Nextcloud? I'm stuck on Nextcloud 23.02, there have ben two versions since and docker updates but still same Nextcloud version. I know there are guides to manually update but they don't look that easy.
Anyone know an easy way of updating the Linuxserver docker version of Nextcloud? I'm stuck on Nextcloud 23.02, there have ben two versions since and docker updates but still same Nextcloud version. I know there are guides to manually update but they don't look that easy.
That's weird, I updated to 23.04 this morning w/ the GUI no problem.
You can try executing this command
docker exec -it nextcloud updater.phar
(this of course assumes your nextcloud container is named nextcloud)
This did the job where the Nextcloud web interface just gave error messages - thanks very much.
Just to add that the download of the Nextcloud update took the best part of an hour on a fast fibre connection using this method in case you're thinking it isn't happening.
Just to add that the download of the Nextcloud update took the best part of an hour on a fast fibre connection using this method in case you're thinking it isn't happening.
Sounds like you've got something else going on, or maybe NC's servers were having issues... Like I said, the upgrade took me about 5min tops from the GUI (and my experience w/ the docker command in the past has been similar)
Just to add that the download of the Nextcloud update took the best part of an hour on a fast fibre connection using this method in case you're thinking it isn't happening.
Although I run it via the Web GUI, just made the update now and it took less than 5m.
If using the docker version (in my case from Linuxserver), first, update the image to the latest (either via docker pull or via portainer).
Restart the container and go to the Nextcloud settings and update from there.
All status is shown on the browser.
Alles anzeigenAlthough I run it via the Web GUI, just made the update now and it took less than 5m.
If using the docker version (in my case from Linuxserver), first, update the image to the latest (either via docker pull or via portainer).
Restart the container and go to the Nextcloud settings and update from there.
All status is shown on the browser.
That's a good point actually... Are you using the :latest tag on your nextcloud image?
That's a good point actually... Are you using the :latest tag on your nextcloud image?
Yes, 😉
Alles anzeigenI wonder if you're dealing with that loopback issue I've read about.
Take a device that is not on your home network (ie, a phone, tablet, etc. that has internet and is not connected to your wifi).. and navigate to your domain
https://www.your-subdomain.duckdns.org
and see if you see the park page. I'm still seeing your park page and it looks like everything set up normal.
I believe it was Zoki who mentioned a while ago some users having a "loopback" issue, where you can't access a domain from the network the domain is hosted on.
Hi I'm sorry for the late reply I've been very busy, I tried what you said and it takes me to this page
Alles anzeigenYes, the dns resolves to you external IP even in the local network (if you do not have a seperat internal DNS server which gives it a different IP).
Some routers do not apply the port forwarding and then you end up on a different port. And you are accessing the router with an internal IP.
I was away and did not follow what is going on, but did you notive the error message abaout an invaild email address and to mee it looks the error mesage is corret.. it has a comma after the gmail.
I dont have the email address error anymore because i changed to KM0201s method. My current error is a PHP error in my nextcloud logs which you can see in one of my later posts
That's how I always do it.. but I think maacom's tutorial is a little different.
I followed your tutorial for this one I believe.
My current situation:
When I access from outside my network I get this:
Hi I'm sorry for the late reply I've been very busy, I tried what you said and it takes me to this page
When I check nexcloud logs I get this:
And I can't access nextcloud interface.
That looks fine
Start w/ getting it to work locally, don't worry about swag, we'll cross that bridge when it's working locally
That looks fine
Start w/ getting it to work locally, don't worry about swag, we'll cross that bridge when it's working locally
Yup I just got to step 11 in your guide and I can still access it fine via my ip:450.
I deployed swag and checked all my logs, no errors reports! Although nextclouddb seems to be stuck on this step and hasnt sent over a "DONE".
here's my swag logs
I'll carry on with the steps now, fingers crossed
Alles anzeigenYup I just got to step 11 in your guide and I can still access it fine via my ip:450.
I deployed swag and checked all my logs, no errors reports! Although nextclouddb seems to be stuck on this step and hasnt sent over a "DONE".
here's my swag logs
I'll carry on with the steps now, fingers crossed
That's a normal ending of a log for mysql/mariadb. Mine has ended w/ that forever..
Yes, 😉
I figured you were..
That's a normal ending of a log for mysql/mariadb. Mine has ended w/ that forever..
OK so in step 11 it says to try go to https://www.YOUR-SUBDOMAIN.duckdns.org but I just get met with "this site cant be reached"
Do I also need SSL on in OMV?
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!