ijuarez

the docker updated (have all my to auto update) and it broke it,. when i visit my instance i get this Internal Server Error The server encountered an internal error and was unable to complete your request. Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report. More details can be found in the server log. damn it

are you going to use a share on your array?

dang chatid, i needed to know where to find it, I finally got mine working. thanks

The agony, so my first install fubar my existing nextcloud because I created the same database on top on the existing. My second try everything install including onlyoffice but due to a browser cache issue i wiped it thinking it was something else. my third everything went fine and onlyoffice installed and worked but realize that users were being put into the cache and the amount of data would filled the cache drive, so i wiped it. This final install moved the /data to share but only office does not work because the document server needs and address and it will not take the address that the reverse proxy is working on UGH! On the bright side im getting better at it.

On last thing, if you put this on your cache drive make sure you map the data to your share otherwise everything you upload will end up on the cache. external storage is ok but not what i want for my users.

So spaceinvader has a few videos on how to fix the errors that you in nextcloud There are some warnings regarding your setup. The reverse proxy header configuration is incorrect, or you are accessing Nextcloud from a trusted proxy. If not, this is a security issue and can allow an attacker to spoof their IP address as visible to the Nextcloud. Further information can be found in the documentation. The "X-Frame-Options" HTTP header is not set to "SAMEORIGIN". This is a potential security or privacy risk, as it is recommended to adjust this setting accordingly. The "Strict-Transport-Security" HTTP header is not set to at least "15552000" seconds. For enhanced security, it is recommended to enable HSTS as described in the security tips ↗. The database is missing some indexes. Due to the fact that adding indexes on big tables could take some time they were not added automatically. By running "occ db:add-missing-indices" those missing indexes could be added manually while the instance keeps running. Once the indexes are added queries to those tables are usually much faster. Missing index "calendarobject_calid_index" in table "oc_calendarobjects_props". Missing index "schedulobj_principuri_index" in table "oc_schedulingobjects". Some columns in the database are missing a conversion to big int. Due to the fact that changing column types on big tables could take some time they were not changed automatically. By running 'occ db:convert-filecache-bigint' those pending changes could be applied manually. This operation needs to be made while the instance is offline. For further details read the documentation page about this. mounts.storage_id mounts.root_id mounts.mount_id Please double check the installation guides ↗, and check for any errors or warnings in the log. Check the security of your Nextcloud over our security scan ↗. Since this is not a LSIO container you can use user abc to run them, does anyone know what is the user that had access to www-data? so the problems can be fixed.

had to reinstall all over, the port 466 issue was a brower cache issue. Solved

this is the same problem i am having, i fubar my LSIO docker so i tried this one, the template does not have the variable for the port so you have to add it. container is 80 and then whatever you want your host to be. My issue is that i am using the proxynet that was suggested a long time ago by spaceinvader. So this docket is sitting on my proxynet, with the variable of port 80 container and 446 for host. Cannot access it, keeps telling me connection refused from the unraid wegui. Looked at the documentation and it states that nextcloud runs on port 80 in the container so it should work. I have not being able to tackle the rest of the install because if this odd glitch.

If you have a large data from a user using sql lite could be very bad. I lost my first Nextcloud install because I choose to do the sql lite I was transferring so much data that the dB just quit and could not recover. Move to mariadb (MySQL essentially) haven’t had a problem. Just my input. Sent from my iPhone using Tapatalk

is hugepages related to thata hugebitch...... I guess I missed that Linus video.

I wanted onlyoffice this was easier than setting up the another docker and having it connect from my original instance.

This is tempting but I already got a working instance.

Now that v3 is stable is the docker going to move to v3 or will you need a new instance?

Yes it was a shit move, an I apologize, but to me, a user, that does nothing to contribute to the developer community makes me a little upset when people make statements that the developers should fix this or that. Folks need to realize that they are not getting paid and they do not own anyone anything. I see you're community developer and I appreciate what you do for the rest of us, keep up the work.

oh so your router(gateway) is forwarding https(443) requests to LE that's on port 12345?

here you go official docker creating the template shouldn't be to hard.

why are you using ports instead of using the proxy confs? I know they may not be one just like what you need but you can modify on to your needs with the ports you need to it can redirect correctly

This is true, we live in a digital world where low lifes are trying to make a quick buck

Good luck to you guys that exploring the docker for the rest of us. Lawrence also did a video but using a vm not docker youtube video For me I just paid the 12 bucks annually and got a family plan, yes it has some limits but for saving my passwords it works.

that happens quite often

I haven't tried it because I'm afraid it would consume all of my ram, i have alot, but if you dont configure it correctly out of the box it will eat all of your cores imagine if you let it free on all of your ram.

upgraded no issues, however after upgrade it started a parity check, even tho it had finish one yesterday before upgrade. meh

So i enable debugging and nothing got no info , but i did notice that when i clicked in details the page just spun waiting for data. Eventually it would timed out. So I deleted the instance all of the associated folders and re-installed and boom the docker begin to work correctly. I think my issue was when the big change happen and I must not followed the directions correctly. Its working thanks

ah, must have skipped over that

I posted about this and never got an answer even included a screenshot so I gave up. Haven’t tried a TDarr yet cause I think it’s too much work but I will have to move on. Sent from my iPhone using Tapatalk