Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

AIO behind caddy still rewrite to 443 port instead of the port I use #3473

Closed
lianqi1998 opened this issue Oct 2, 2023 · 2 comments
Closed
Labels
0. Needs triage Pending approval or rejection. This issue is pending approval. bug Something isn't working

Comments

@lianqi1998
Copy link

lianqi1998 commented Oct 2, 2023

Steps to reproduce

  1. My ISP block 80, 443 port
  2. Add caddy reverse proxy config with ACME DNS-challenge and open 20000 to replace 443. Caddy can get cert and run well.
  3. Use AIO behind caddy with --env SKIP_DOMAIN_VALIDATION=true
  4. Open https://my.domain:20000 Nextcloud will rewrite to https://my.domain/login
  5. I can enter Nextcloud panel after I add port manually. And after login the matter disappeared.
  6. After I modified "domain": "my.domain:20000" in configuration.json as folder nextcloud_aio_mastercontainer/_data/data/ It seems fixed (I'm not sure, I changed a lot)

Expected behavior

After acess Nextcloud with specific port I think AIO should not rewrite adress to 443

Actual behavior

With right reverse proxy config, Nextcloud still rewrite adress as default (443).
After login the matter disappeared, so I guess it's a bug

Host OS

debian 11

Nextcloud AIO version

AIO v7.2.1

Current channel

latest channel

Other valuable info

By the way, I wonder to know if I modified "domain": "my.domain:20000" in configuration.json with port information directly, it will produce other problem?
Thank You for Your Patience.

@lianqi1998 lianqi1998 added 0. Needs triage Pending approval or rejection. This issue is pending approval. bug Something isn't working labels Oct 2, 2023
@lianqi1998 lianqi1998 changed the title AIO behind caddy still rewrite to 443 port AIO behind caddy still rewrite to 443 port instead of the port I use Oct 2, 2023
@Zoey2936
Copy link
Collaborator

Zoey2936 commented Oct 2, 2023

@lianqi1998
Copy link
Author

lianqi1998 commented Oct 3, 2023

If port 443 and/or 80 is blocked for you, you may use the ACME DNS-challenge or a Cloudflare Tunnel

I think perhaps AIO support other port, by get cert by ACME DNS-challenge?

https://github.com/nextcloud/all-in-one#are-other-ports-than-the-default-443-for-nextcloud-supported - also the :2000 could cause problems↳

So that means AIO can only run on 443 ?
If AIO only support 443, maybe emphasize the consideration that even if use the ACME DNS-challenge or a Cloudflare Tunnel, AIO still don't work on the environment as port 443 and/or 80 is blocked is better

But what confuses me is AIO will work after login. It seems like it is a bug happens on login.
And could I know why abandon other port support, it looks as if once solve the problem while login, AIO will run other port behind reverse proxy.

@nextcloud nextcloud locked and limited conversation to collaborators Oct 3, 2023
@szaimen szaimen converted this issue into discussion #3477 Oct 3, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
0. Needs triage Pending approval or rejection. This issue is pending approval. bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants