为lmnp，owncloud Nextcloud 增加外网ipv6访问

bcahlit

NextCloud has been set up, but the Internet IPv6 is lacking and cannot be accessed. Moreover, the optical modem does not have the function of port mapping, and V4 is not good. Previous experience with v6 access to ftp, should be ok.

Method: Edit inside the router:

vi /opt/bin/sh_onmp.sh

Original line 1846:

sed -e "s/.*listen.*/    listen $1\;/g" -i /opt/etc/nginx/vhost/$2.conf

Modified 1846 behavior:

sed -e "s/.*listen.*/    listen $1\;\n    listen [::]Delete 1\; /g" -i /opt/etc/nginx/vhost/$2.conf
(Because $1 will become an emoji when it is connected together, everyone can delete the kanji in the middle by themselves)

It is to add IPv6 listeners to NGINX, and after restarting LNMP, you can use IPv6 to access NextCloud on the Internet. Next, follow the prompts to add a trust.

--------------------------------------- The above is enough to solve the problem, and the following is the solution

The process of solving,First of all, google problem,Nextcloud says it supports v6 by default,But I can access the web management interface with v6 after I turn off the firewall,But I can't access nextcloud.。。 I think there's a problem.

Later, I thought it was a problem with nginx, so I searched for the configuration of nginx.

find | grep nextcloud.conf # Locate the configuration file

/opt/etc/nginx/conf/nextcloud.conf

However, there is no listening configuration in it, so I look for the configuration file of nginx

There is 1 sentence in cat ./etc/nginx/nginx.conf

include /opt/etc/nginx/vhost/*.conf;
I found that there is indeed a listening port in /opt/etc/nginx/vhost/Nextcloud.conf.

Manually add an IPv6 listener, restart LNMP, and find that IPv6 still cannot be accessed. Take a look at the configuration file. The ipv6 I added by myself is gone...

Thinking that there is a script, I found the point to be modified in the big git repository of H, added it, and restarted it.

I use the new three performance 1 general, I feel that this thing is not very suitable, barely enough. If you want to transfer files, filemanager is more lightweight.

szkorman

No wonder the various plug-ins in the web construction can only be accessed by IPv4 external network IPv6 Even if it is a public network, it can't be accessed It turns out that this is the reason But I followed your tutorial IPv6 still can't be accessed I built on the new three, such as qBit, these plug-ins can be perfectly accessed with IPv6 domain names I don't know why? Thank you

szkorman

I also want to ask the landlord, if I want to let IPv6 access to z-blog, how should I set it up? Thank!