-
Notifications
You must be signed in to change notification settings - Fork 712
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs Improvement - Accessing NextCloud after AIO setup, Reverse Proxy Improvement #5926
Comments
Hi, I agree on this but how can we improve the situation? Simply adding a chapter to the top of the rp docs how AIO works internally maybe? Do you have some ideas? |
Can I raise PRs for this & you can review those |
Yes, please do. Sounds good :) |
Hi @surapuramakhil any update here? |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
okay |
@surapuramakhil any update here? |
Steps to reproduce
you will realize that next cloud AIO is manager for next cloud.
Expected behavior
you shouldn't be facing this issue
Actual behavior
you are clue less - how you can access Next Cloud instance that you made setup using AIO
Other information
Host OS
Output of
sudo docker info
Docker run command or docker-compose file that you used
Other valuable info
The text was updated successfully, but these errors were encountered: