Phabricator not rendering resources over https

earthfront 2016-01-06 03:57:17 UTC #1

Setup: Bitnami Phabricator on AWS instance, installed around a week ago.

Actions taken:
* A TLS certificate was manually installed and configured (using directions on the bitnami phab wiki).
* All possible uri's listed in the wiki were set to https://[my-domain].

Problem:
Chrome and Firefox did not render the UI, but only text, identical to this problem: https://community.bitnami.com/t/phabricator-installed-but-not-rendering-the-ui-only-bare-text-links/38827
That solution did not apply to this case, as this is a prepared image, not an installer.

Solution:
Set the phabricator option security.alternate-file-domain to the https url.
Explanation: https://secure.phabricator.com/book/phabricator/article/configuring_file_domain/
Though it works, this does not seem like the correct solution. There should be a more elegant or documented solution to this problem.

Please advise what the root problem might be.

agonzalez 2016-01-06 17:42:00 UTC #2

Hi @earthfront

We have update the Bitnami Wiki Page with new steps to configure HTTPS properly: https://wiki.bitnami.com/Applications/Bitnami_Phabricator#How_to_enable_SSL.3f

That property is not the correct way to set phabricator to serve static resources as Javascript and images of the UI.

Best regards,
Andres

earthfront 2016-01-07 02:45:44 UTC #3

Thanks for the quick response!
My post should have included that the security.alternate-file-domain was set to a "http://[domain]:43" address somehow. Perhaps this was through setting the base-uri option.

I deleted the security.alternate-file-domain config option and restarted. The page loaded successfully. My project's static resources are not CDN hosted.

To note:
* There is a warning now when logged in as administrator: "Alternate File Domain Not Configured
Increase security (and improve performance) by configuring a CDN or alternate file domain."

What is preventing this option from being null to begin with?
Does the command "/apps/phabricator/bnconfig --machine_hostname NEW_HOSTNAME" also set base-uri and alternate-file-domain?

jdrios 2016-01-08 18:07:51 UTC #4

Hi,

If you are not using a CDN (and you don't want to use it) to serve the static resources, please run the following command:

sudo apps/phabricator/htdocs/bin/config delete security.alternate-file-domain

Note:
Be sure you are in the installdir folder (/opt/bitnami usually)

I hope it helps

earthfront 2016-01-09 01:38:59 UTC #5

Hi jdrios! Thanks, deleting that option solved my problem.

There is a new question now.
The alternate-file-domain option is also set using the command "/apps/phabricator/bnconfig --machine_hostname NEW_HOSTNAME" (I guess).
Why?

If one uses the above bnconfig command AND:
If one does not use a CDN:
this option does not need to be set. One must delete the alternate-file-domain option. This is an unnecessary step for configuration.
OR
If one uses a CDN:
The CDN probably is not the same machine's hostname. Therefore, one must set the option to another hostname anyway.

So, there is no need to set this option when running the bnconfig command.

Can we disable this "feature"? More precisely: can we disable setting the option "security.alternate-file-domain" when running the command "/apps/phabricator/bnconfig --machine_hostname NEW_HOSTNAME"?

jdrios 2016-01-11 12:37:14 UTC #6

Hi,

I wasn't able to reproduce the --machine_hostname issue. I'm sure we are not modifying anything else with that option.
To ensure that I launched the bnconfig --machine_hostname in a clean Phabricator Google VM. Also, I launched sudo apps/phabricator/htdocs/bin/config delete security.alternate-file-domain and I checked that key wasn't set in my local configuration.

Phabricator doesn't show any message related to the alternate-file-domain after doing those actions (I checked before the config delete command too)

If you are able to reproduce the issue, please let us know.

earthfront 2016-01-12 04:18:58 UTC #7

To test, I downloaded the Phab. VM image from the bitnami website.

Upon starting the VM, I stopped the services:

sudo /opt/bitnami/ctlscript.sh stop

The untouched image loaded into VirtualBox has option values:

phabricator.base-uri : http://10.0.2.15:80/
security.alternate-file-domain : http://10.0.2.15:80/

(Perhaps that IP is mine and was configured on boot, or it comes on the VM image?)

Then, apparently the apps need to be started for bnconfig to work:

sudo /opt/bitnami/ctlscript.sh start

Then I ran the bnconfig tool to change the machine_hostname option to example.com:

apps/phabricator/bnconfig --machine_hostname example.com

Now the option values are:

phabricator.base-uri : http://example.com:80/
security.alternate-file-domain : http://example.com:80/

The image used was provided here:
https://bitnami.com/stack/phabricator/virtual-machine

Conclusion: setting machine_hostname via bnconfig appears to write the same hostname to security.alternate-file-domain.
If you'd like a transcript of my session, I can SSH and copy/paste the commands and output leading to this. Beyond that, I can't spend any more time on this.

Thanks.

jdrios 2016-01-12 17:03:37 UTC #8

Hi,

I did the same steps and I couldn't reproduce it. I really appreciate your help and attention though. If some user finds an issue like this, this post will be so useful.

Feel free to write us back with any question you may have

earthfront 2016-01-13 04:00:25 UTC #9

Well, I'm flummoxed.

I reproduced the issue successfully yet again on a fresh VirtualBox mount of the virtual disk in:

bitnami-phabricator-20151125-0-ubuntu-14.04.zip

This was downloaded from the link mentioned in the above post.
Using the "script" command, I captured a log of the repro. here:
http://pastebin.com/raw/jC5j5mGP

A few commands I typed got borked because "script" captures escape sequences and I cat'd and copy/pasted them. You can guess what they mean.

I don't see the source of "bnconfig" is available anywhere. Is that something you can look at? I thought to grep the source for "machine_hostname" and see exactly what that thing does.

Hopefully you can reproduce and solve this. Thanks for your time.

jdrios 2016-01-14 16:19:41 UTC #10

Hi,

May thank you for being curious in this case. Checking with that VM I've been able to check that is because the version. They fixed the issue in some version after that one. The last version that we have works fine.

Finally, we got this.

jsalmeron 2017-11-23 09:27:50 UTC #11

A post was split to a new topic: Phabricator HTTPS content issue

jsalmeron 2017-11-23 09:29:01 UTC #12

Bitnami provides free all-in-one installers, virtual machines and cloud images for popular open source applications. Get them now!