Canvas-rce-api Problems

[bigvikingjim]

Summary: Tried installing Canvas (stable version) on Ubuntu 18.04, 16.04 and on the bitnami stack all suffer with the same issue. On the bitnami support ticket https://community.bitnami.com/t/rich-content-editor-and-passenger/70780/18 there are other users using other OS's who also have the same issue. Problem manifests itself in the Files tab on the RCE editor being greyed out and the Links tab whilst accessible fails to see any links

Steps to reproduce:

1. Login to Canvas
2. Create a page
3. Try to edit that page

Expected behavior:

Files tab on the RCE editor should be accessible and links should not fail

Actual behavior:

Both do not work on any of the three installation I have

Additional notes:

This wasn't a problem before the RCE release became production. As a short term fix as this is urgent for us how can we install the pre-production version before may/june of this year when the RCE server became mandatory.

Originally thought it was the bitnami stack so I took that out the equation. Currently on ubuntu 16.04 failing when trying to install rce server with docker. Saying ECOSYSTEM var expected but not set. Yet its in the ENV file and even shows when running printenv from shell.

[simonista]

Hi @bigvikingjim, you need to be running https://github.com/instructure/canvas-rce-api now to support this functionality. That readme has instructions, and it looks like there are some threads in the google group which may also be helpful: https://groups.google.com/forum/#!searchin/canvas-lms-users/rce$20api%7Csort:date

Unfortunately we don't have anything to do with the bitnami release, so I don't know what it would take to support it natively there. It looks like this was first required in the release/2019-05-11.01 release tag, so you'd want to run a version (based on git tags) from before then if you need to go that direction.

[bigvikingjim]

Hi Simon, Thank you for the advice. I have installed the canvas-rce-api service but having some issues. I will try and progress that but would you be able to advise me on how to install the older 2019-05-11 version?. Is it as simple as following the install guide and instead of checking out the stable version just check out a version before that date ? Kindest Regards, Jim From: Simon Williams <[email protected]> Sent: 12 November 2019 20:41 To: instructure/canvas-lms <[email protected]> Cc: James Ling <[email protected]>; Mention <[email protected]> Subject: Re: [instructure/canvas-lms] Canvas-rce-api Problems (#1523) Hi @bigvikingjim<https://github.com/bigvikingjim>, you need to be running https://github.com/instructure/canvas-rce-api now to support this functionality. That readme has instructions, and it looks like there are some threads in the google group which may also be helpful: https://groups.google.com/forum/#!searchin/canvas-lms-users/rce$20api%7Csort:date Unfortunately we don't have anything to do with the bitnami release, so I don't know what it would take to support it natively there. It looks like this was first required in the release/2019-05-11.01 release tag, so you'd want to run a version (based on git tags) from before then if you need to go that direction. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#1523?email_source=notifications&email_token=ANCYBMWSAVDQZIJATMPTQ33QTMIF3A5CNFSM4JHIPNDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOED33I2A#issuecomment-553104488>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANCYBMSNSLUT5A3BW6RUQKDQTMIF3ANCNFSM4JHIPNDA>.

[simonista]

Hi Jim, it depends a bit on what version you are running right now, and whether you have run database migrations for that version. The risk of going backwards is reverting the database schema to the point it was then. You'll want to build a list of migrations that have run between the version you're going back to and the version you are on now, and carefully study what will happen by reversing them.

I think trying to move forward with getting the canvas-rce-api working is the less risky option. Let us know how we can help in the google group or on IRC, we're in #canvas-lms on Freenode.

[bigvikingjim]

Hi Simon, Forgive me for replying directly but I am in need of some help urgently even if I have to pay someone to sort it out for me. What I want to do is Run latest Canvas on the same server as the RCE api. I have followed instructions and managed to get things running if I serve them on the same port as canvas 80/443 which I didn’t expect. But I have 2 SSL certs and they are getting confused. I tried running on separate ports 8080/993 and the hello from RCE server does not work. So I am in a vicious circle I can get it all up on the same ports but SSL gets confused or I start it on separate ports and it fails the RCE hello tests. The browser has strange errors in too in the developer console. In general not a happy installation (Ubuntu, 16.04 on Azure using letsencrypt). SSL certs check out ok on SSL Labs. So do you or anyone you know have any suggestions?. If required I can provide full configs/screenshots and even remote SSH access via teamviewer or AnyDesk if I need to pay some to sort it out. Ideally, the college wants it sorted this week hence the direct email and urgency and I am out of ideas. Appreciate any help or recommendations you can provide. Kind Regards, Jim From: Simon Williams <[email protected]> Sent: 13 November 2019 15:57 To: instructure/canvas-lms <[email protected]> Cc: James Ling <[email protected]>; Mention <[email protected]> Subject: Re: [instructure/canvas-lms] Canvas-rce-api Problems (#1523) Hi Jim, it depends a bit on what version you are running right now, and whether you have run database migrations for that version. The risk of going backwards is reverting the database schema to the point it was then. You'll want to build a list of migrations that have run between the version you're going back to and the version you are on now, and carefully study what will happen by reversing them. I think trying to move forward with getting the canvas-rce-api working is the less risky option. Let us know how we can help in the google group or on IRC, we're in #canvas-lms on Freenode. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#1523?email_source=notifications&email_token=ANCYBMW32EII2PONKAIWF2DQTQPURA5CNFSM4JHIPNDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOED6TSTI#issuecomment-553466189>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANCYBMVYXCRBYKUYB7VDGITQTQPURANCNFSM4JHIPNDA>.

[simonista]

Hi @bigvikingjim, I'm sorry but I'm really not sure how to help. I still think you'll have better luck in IRC, it looks like @grahamb tried responding to you there yesterday but you never answered his question.

We run this API on a separate server, so I'm not sure about the setup you are describing. I did find this PR on the repo that looks like it might potentially be related to the problem you're seeing? instructure/canvas-rce-api#5. You could try applying that and seeing if it helps.

Sorry not to be more help!

[grahamb]

Agree with @simonista - @bigvikingjim, you should come back to the IRC channel and we can try to help you there. We also run the RCE on separate servers at our site, but I can't imagine why you wouldn't be able to run them on the same one, other than some sort of configuration issue. The IRC channel tends to be most active during business hours in the pacific & mountain time zones (UTC-8, UTC-7).

[eduhl17]

Hola, esto me ayudo a mi:
sudo a2enmod proxy
sudo a2enmod proxy_http
sudo a2enmod proxy_balancer
sudo a2enmod lbmethod_byrequests
sudo service apache2 restart

instructure/canvas-rce-api#6