-
Notifications
You must be signed in to change notification settings - Fork 178
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
Blank page after fresh install on raspberry pi #1354
Comments
Hi @Rilnaista thank you for opening an issue! By having a look at your command, did you replace the dummy text from the docs
Resulting in modifying your command to something like: PROXY_HTTP_ADDR=0.0.0.0:9200 \
OCIS_URL=https://owncloud:9200 \
PROXY_TRANSPORT_TLS_KEY=server.key \
PROXY_TRANSPORT_TLS_CERT=server.crt \
KONNECTD_TLS=0 \
./ocis server
Would you please be able to on a different terminal (with ocis running) run |
Hi @refs ! Thank you for your quick reply. I modified the command as you described. But there is no change in the behavior. I get the same error message in my browser javascript / ressources console. When I run
I start the fullstack ocis via
The service comes up and starts the microservices in a row - mostly looks fine, but there are three warnings - are they important?
|
It seems to be a duplicate issue to #1085 but there is no solution documented ... |
indeed, we solved it internally. Let me fetch the fix and post it later / tomorrow :) |
TY for your assistance! I'll be patient :) |
I have the same problem |
Hi @Rilnaista, apologies for taking me 5 days to get back to the issue, we've had a busy week. We've had some setbacks with mDNS as a default service registry, so another approach is to use
Installing etcd
And for some reason, etcd needs some fixes that are described here: etcd-io/etcd#10677 (comment) which is:
And finally start the etcd service: either Note that this step is not necessary, you could also go for the default mDNS. For that, you need to make sure ahavi-daemon is installed and started but potentially run into firewall issues. Start oCIS with etcd as service registrySet PROXY_HTTP_ADDR=0.0.0.0:9200 \
OCIS_URL=https://owncloud:9200 \
PROXY_TRANSPORT_TLS_KEY=./server.key \
PROXY_TRANSPORT_TLS_CERT=./server.crt \
MICRO_REGISTRY=etcd \
KONNECTD_TLS=0 \
./ocis server Sadly I haven't yet been able to entirely reproduce it on my machine since I'm using dockerpi but please give this a go, I'd be happy to hear back from you after trying this out. |
Thank you! Using |
So I'm really annoyed by now. I've been trying to get the software up and running for 1 week. The beta version of 1.0.0 reveals at least the webgui. As of version 1.0.0 RC1 white screen. When trying to log in, the developer tools Another idea? |
That's indeed annoying. I will dig into this this week, perhaps the docs are outdated and need a revamp. Will dog into your config and reproduce it on my setup :) we could also debug on a Zoom call if you have the time |
I would love to debug with you just is my English disaster :D |
And that's perfectly fine! Let me write you tomorrow |
@Aruscha I tried your setup on my machine and am confident it should work on your Pi when we switch the service registry over to |
So for me it runs in a VM or In an LXC CONTAINER |
@Aruscha It's okay, I can try my best German :) do you have an email I can send you the zoom link? |
@refs Have you tried running the Docker container?
The problem there looks the same - if it is the same issue, it can no be specific to @Aruscha setup. I am using an Intel NUC (eq.) with Ubuntu Server 20.10. |
Just tried It doesn't smell as it is the same issue. |
Ok - that is interesting. I thought it was a general issue so I did not try it any further. I ran the Docker image under Windows and there it is starting up. |
I had just made a clean install on a clean raspberry pi (2021-01-11-raspios-buster-armhf-lite) full updated / upgraded via
curl https://download.owncloud.com/ocis/ocis/1.0.0/ocis-1.0.0-linux-arm --output ocis
After that I started the service via
-/ocis server
I stopped the service via STRG+C and edited the generated config/identifier-registration.yaml like descibed at https://owncloud.github.io/ocis/deployment/basic-remote-setup/ to access this owncloud from my PC.
After editing the yml file I started the server with the following command:
PROXY_HTTP_ADDR=0.0.0.0:9200 \ OCIS_URL=https://owncloud:9200 \ PROXY_TRANSPORT_TLS_KEY=./certs/your-host.key \ PROXY_TRANSPORT_TLS_CERT=./certs/your-host.crt \ KONNECTD_TLS=0 \ ./ocis server
I cleared the cache in my browser and typed in the hostname and got a blank screen. I took a look in the console and saw that owncloud tried to load an js-Library from localhost.
2core.bundle.js:18 UserManager.getUser: user not found in storage core.bundle.js:18 JsonService.getJson: network error t.error @ core.bundle.js:18 localhost:9200/.well-known/openid-configuration:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT core.bundle.js:18 Uncaught (in promise) Error: Network Error at XMLHttpRequest.s.onerror (core.bundle.js:18)
I followed all described steps to access own cloud via remote. It didn't work as expected / described. Don't know it there is an bug in the documentation or software.
Hope I provided all needed information to reproduce this error.
The text was updated successfully, but these errors were encountered: