Again thanks so much for helping me out.
Again thanks so much for helping me out.
Thanks again for all the help.
Is there some reason I can't just add to the stack in the portainer web editor and then redeploy? I have already updated the bitwarden.subdomain file.
I already had the vandoebitwarden setup in duckdns. I have a backup of the docker-compose.yml that I made earlier when I backed up the container and config files.
Acording to this source:
Reviewing this source it appears that it is a setup not using HTTPS. I 've gotten Bitwarden to work multiple times without https but most of the setups recommend using self-signed certs or let's encrypt. I've tried both but couldn't get either to work. Nextcloud is already running with nginx and let's encrypt so I was hoping to be able to build off that setup to run Bitwarden as well.
You also mentioned before that you can't use the port twice?
current swag is mapping 81:80
and the bitwarden you proposed is mapping 8005:80
Thanks for coming up with these options
So I could just add this section to my existing Nextcloud/swag docker-compose? How does it connect with the existing ssl certs that are created by existing docker-compose
The dani Garcia bitwardenrs is the one I have been trying to install.
Here is the docker-compose file. I would sure appreciate the addded help for bitwarden. I have been going in circles for a while.
Thanks guys I have been changing too many things at once. What happened is I did not get a complete copy of my docker compose file. It was missing the tail end of the swag portion including port mapping. After cleaning up my port mapping I have next cloud working. Can I use this same nginx set up to add a self hosted bitwarden? Part of my problem was I was trying to get this going at the same time with overlapping ports.
None of this should be needed if you are using your old config folders.
Looking back I can see that now. It did seem like I had to change the nextcloud.subdomain.conf and I was surprised that the config.php file was already correct so I went back and compared the nextcloud.dubdomain.conf with back up file and they appear to be the same. Here is the log from the swag container.
Any thoughts on this error. I made no configuration changes to the router prior to this.
No more thoughts on how to get it working?
The usual can't reach this site error
You had to know this wouldn't go without a hitch. The steps below are from a previous session that I am following to re-create nextcloud. I have the containers up and running. I ran into trouble at step 2 below. When I first did it I got the correct page where you accept security risk and proceed. When I select my IP to proceed it errors out and I notice that chrome tries to default to my duck dns (photovandoe) so I thought maybe this was a cache problem. Tried it again with Microsoft edge and got the same problem. I have skipped ahead and fixed the nextcloud.subdomain file and the config.PHP file
1. Create all the directories and make all adjustments you need in docker-compose (you might want to delete old directories if you can, since you seem to be having issues), then deploy the stack/docker compose file. If you use this set up exactly, in your router you'll need to make sure port 457 is forwarded to 443 and port 91 is forwarded to 80Once that is done, you can complete a basic setup of Nextcloud, or move on to set it up with duckdns subdomains.9. Save (Contrl x ) and and use backspace to erase the ".sample" extension. Hit enter then Y to save..
I had a thought about just moving all the files to the new docker folder location instead of re-deploying it all. Any thoughts on whether this might work?
I'll give that a shot.
backup all your config and data folder you are using for dockers (preserving permissions, e.g. with rsync -a)
Not sure how to do this.
deploy the docker using the yaml files from the previous installation (this should use your existing config and data folder)
I had help from KM0201 when I was unsuccessful installing nextcloud. He worked on it with teamm viewer for about 8 hrs before succeeding. I'm pretty sure I can't repeat this. It was just the yaml file there were several modifications along the way.
Looks like that worked ok.