-
-
Notifications
You must be signed in to change notification settings - Fork 661
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
network error while running the script #14
Comments
What output do you get from And thanks for reporting! |
ping @cketan |
Hi, thanks for reply i have changed the auto ip to manual ip and tried to re-run the script and its worked :) |
But still, if it didn't work with auto IP what was the issue so that I can solve it? |
i have installed the pre-build VM on hyper-v, VM has taken auto IP as 192.168.1.108 and windows server has assigned the IP in Virtual network as 192.168.1.102 due to both system miss configuration VM has unable to connect to internet then I have assign the manual IP in VM as 192.168.1.102 then it is able to access the Internet. |
Ok, so it got an IP, then there isn't a problem with the VM then. Good to know anyway. :) |
Try to set it manually in /etc/network/interfaces and remove "bash ip.sh" Then run the install script. Op vr 26 aug. 2016 10:03 schreef stuffedmonkey notifications@github.com:
Met vriendelijke groet, E. Holm |
Ok. Where do i find nextcloud_install_production.sh? |
Its in /var/scripts Op vr 26 aug. 2016 18:01 schreef stuffedmonkey notifications@github.com:
Met vriendelijke groet, E. Holm |
@ezraholm50 negative. In that folder I only have history, instruction, nextcloud_startup and setup_secure.... |
Once you run the first setup, the install script gets deleted. Enable DHCP in your router and make sure your hypervisor is set to bridged mode, download the VM again and start over. |
i have installed the pre build Nextcloud server in VM while running the script it was showing the error but when check the cloud ip in explorer it is accessible and showing apache home page please help me to resolve this issue.
The text was updated successfully, but these errors were encountered: