I started thread about this issue in Nov 19 but was too busy that time to follow closely.
Last Richard's suggestion was:

"
#define ERR_HTTP_TRANSIENT -184
// HTTP errors other than 404 and 416
So, set <http_debug> and find out what the actual http error is. Not 404 or 416, obviously.
"

Currently I installed fresh NativeBOINC app on new-old device HTC Bravo ... and have same issue as with my another HTC Evo - client cant't even attach to project.

Same code of error.
In log file I see:
Fetching configuration file from http://setiathome.berkeley.edu/get_project_config.php

Project communication failed: attempting to access to reference site

Internet access OK - (and so on)

Abrolutely the same as another HTC.

But, I also have old Viewsonic tablets with NativeBOINC installed - they fetch work from SETI just OK....

Im'm not sure I can set <http_debug> under NativeBOINC. And would like some more guidance if possible.

There was suggestion to edit host file.
Seems I found where it resides and can edit it
currently it has
127.0.0.1 localhost
default record.

What should I add to this to help to connect to SETI servers?

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

My current set has

# 208.68.240.118	setiboincdata.ssl.berkeley.edu	# upload server Aug 2017
# 208.68.240.119	boinc2.ssl.berkeley.edu		# download server Aug 2017
# 208.68.240.126	setiboinc.ssl.berkeley.edu	# scheduler Aug 2017
# 208.68.240.127	boinc2.ssl.berkeley.edu		# download server Aug 2017
# 208.68.240.110	setiathome.berkeley.edu		# website Aug 2017

But your device really should have access to a DNS server - either via static IP configuration or via DHCP.

Have you updated ca-bundle.crt to the current version? The one supplied with NativeBOINC stopped working for me a while ago, at least for SETI.

You can use TotalCommander to view or edit cc_config or copy a new ca-bundle.crt to the device, but I think it needs to be rooted.

---

Have you updated ca-bundle.crt to the current version? The one supplied with NativeBOINC stopped working for me a while ago, at least for SETI.

You can use TotalCommander to view or edit cc_config or copy a new ca-bundle.crt to the device, but I think it needs to be rooted.

Unfortunately it installed into internal memory so no access via TC (phone not rooted). Will move to SD and try then, thanks all!

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

Have you updated ca-bundle.crt to the current version? The one supplied with NativeBOINC stopped working for me a while ago, at least for SETI.

You can use TotalCommander to view or edit cc_config or copy a new ca-bundle.crt to the device, but I think it needs to be rooted.

Today I managed to enable HTTP debug (as Richard suggested long ago) on HTC Evo with NativeBOINC on SD card. It suffers from same issues.
Can't connect to E@h too.

So, I got strings in log about certificate refusal. Your hint should work.
Will check it in few minutes.

EDIT: not so easy... only data folder on SD, but not binary, And certificate file in binary folder...
Any ideas how to update it on non-rooted phones?

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

Any ideas how to update it on non-rooted phones?

What if I replace that file just inside APK pack? Will it fail with CRC error?

Maybe to disable HTTPS ? Switch to HTTP 1 or smth alike?

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

Unfortunately no idea... never played much around with not rooted phone. Updating inside the APK should actually also update the CRC, just like if you repack a zip or whatever, otherwise it would be pointless to have the possibility to update APKs at all, but I have never done it myself, so this is just a guess.

---

Unfortunately no idea... never played much around with not rooted phone. Updating inside the APK should actually also update the CRC, just like if you repack a zip or whatever, otherwise it would be pointless to have the possibility to update APKs at all, but I have never done it myself, so this is just a guess.

I'm afraid APK has some sort of additional (versus ordinary archive) CRC/signature check to prevent virus /trojan addition to well-known apps. But worth trying. I have NativeBOINC APK so will try...

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.