I have been checking closer the tutorial you provided us and I am afraid this issue is not in our side.
This is what I have configured in the tutorial:
- Logged in the instance by ssh.
- Modified the
redis.conf configuration file (which is in
/opt/bitnami/redis/etc/redis.conf) changing the port from 0 to 6379:
Note: First, execute
sudo /opt/bitnami/ctlscript.sh stop redis and
sudo /opt/bitnami/ctlscript.sh start redis after you modify the config file.
# The server only accepts connections from clients connecting from the
# IPv4 and IPv6 loopback addresses 127.0.0.1 and ::1, and from Unix domain
# By default protected mode is enabled. You should disable it only if
# you are sure you want clients from other hosts to connect to Redis
# even if no authentication is configured, nor a specific set of interfaces
# are explicitly listed using the "bind" directive.
# Accept connections on the specified port, default is 6379 (IANA #815344).
# If port 0 is specified Redis will not listen on a TCP socket.
# TCP listen() backlog.
# In high requests-per-second environments you need an high backlog in order
# to avoid slow clients connections issues. Note that the Linux kernel
# will silently truncate it to the value of /proc/sys/net/core/somaxconn so
# make sure to raise both the value of somaxconn and tcp_max_syn_backlog
# in order to get the desired effect.
Then, I started with the tutorial configuring the developer key with these paremeters:
And configured the Commnons app with:
Note: Also, please, check that the URL that I have configured differs from the one of the tutorial. There is another Github issue about that.
Now, if you introduce the developer ID/key you will see the blank page, but if you go to the Apache logs (
/opt/bitnami/apache2/logs/access_log) you will see this entry:
188.8.131.52 - - [25/Oct/2017:11:25:18 +0000] "GET /login/oauth2/auth?client_id=10000000000001&redirect_uri=https%3A%2F%2Flor.instructure.com%2Fapi%2Foauth%2Fcanvas%2Faccount-setup-callback&state=bcd19b63aa134953bee44d02be4763a3%2Csetup&response_type=code HTTP/1.1" 302 108
If you get access to:
You will be redirected to the instructure API and you will se the screenshot you were suposed to see. But then you will get an HTTP 502 of their API.
This is an issue that currently has been reported in the community forums of CanvasLMS:
So, as this seems to be an internal issue with the CanvasLMS API, could you please post an issue in the CanvasLMS forums?