Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteIf BOINC clients at one site can reach their science projects and users can open BAM in a browser, but the clients cannot contact BAM as an account manager, do not assume BAM is down. First compare a failing client with a working one, confirm the configured endpoint is https://bam.boincstats.com/, and have the network administrator inspect outbound filtering, proxy handling, and firewall logs for the BOINC process at the failure time. The historical case behind this symptom did not establish a single root cause or a confirmed fix.
What the symptom tells you—and what it does not
BAM! is BOINC’s account manager for project accounts, preferences, teams, and computer connections. BOINC’s current project listing identifies its endpoint as https://bam.boincstats.com/.
Successful browser access proves only that a browser request is allowed. Successful communication with attached science projects proves that those project requests work. Neither observation proves that the BOINC client’s account-manager request uses the same proxy, filtering rule, process identity, protocol, or route. This distinction is an inference from the documented network model and the historical one-location report, not proof that any particular firewall, ISP, DNS service, proxy, or BAM server caused the failure.
Why outbound network policy is the leading hypothesis
David P. Anderson, BOINC’s principal investigator and director, describes BOINC in BOINC: A Platform for Volunteer Computing: “All communication uses client-initiated HTTP; thus the BOINC client works behind firewalls that allow outgoing HTTP, and with HTTP proxies.”
#1 Best Overall
Because the client initiates the connection, an administrator needs to examine the affected location’s outbound policy rather than checking only whether an inbound port is open. Web filters can classify the BOINC executable differently from a browser, and a proxy may require configuration that the client does not have. These are hypotheses to test; the available case evidence does not confirm either one.
Collect comparable evidence first
Use one affected computer and one known-working computer, preferably during the same period. Record the following before changing settings:
- BOINC version and operating system
- The exact account-manager URL shown in the client
- The local time and time zone when contact failed
- The complete account-manager error text
- BOINC startup messages and relevant client-manager log entries
- Whether ordinary project downloads, uploads, and scheduler contacts succeed
BOINC’s support guidance asks users to provide startup messages and check firewall allowances for BOINC executables. Preserve the original text rather than paraphrasing a generic “connection failed” message; timestamps let an administrator match the client event with network logs.
Step 1: Verify the account-manager endpoint
- Open the account-manager configuration in the BOINC client and inspect the URL, not just the page that a browser opens.
- Set or confirm the endpoint as https://bam.boincstats.com/.
- Retry once and record the resulting message and time.
Older configurations or reports may show an HTTP address. A browser redirect does not demonstrate that the BOINC client is using the same address or protocol, so verify the value inside BOINC itself. Debian’s BOINC documentation also illustrates attaching an account manager with the HTTPS BAM address; exact commands and flags vary by installed BOINC version.
Step 2: Compare the two locations’ outbound handling
Firewall and web-filter logs
Ask the network administrator to search the affected site’s firewall and web-filter logs for the BOINC host, process or application identity where available, destination, and recorded failure time. Compare those entries with the working site. Look for a deny, reset, authentication challenge, policy category, TLS inspection action, or absence of any observed request.
Proxy configuration
Determine whether the affected network requires an HTTP proxy and whether BOINC is configured to use it. A browser may authenticate to or auto-discover a proxy while the BOINC service does not. Do not treat a browser’s successful login as evidence that the client has equivalent proxy credentials or settings.
Firewall rules for BOINC executables
Review rules applied to the BOINC client and manager executables. BOINC help guidance discusses allowing its executables, but historical forum examples of TCP ports are not a universal BAM firewall rule. Avoid creating broad permanent exceptions based only on an example port number.
Step 3: Use DNS and route checks as observations, not conclusions
From both locations, record the DNS result for the BAM hostname and any route or connection differences at the same time. A difference can narrow the investigation, but the cited case does not establish DNS or routing as the cause. Do not declare a DNS fault merely because two sites return different addresses, and do not infer that a successful browser lookup represents the BOINC process’s complete path.
Recommended Free Tools
Step 4: Retest with least privilege
After the administrator identifies a specific policy difference, make the smallest rule or proxy correction that permits the required outbound request. A short, controlled firewall test may be used at the administrator’s discretion, but permanently disabling protection is unsafe and a temporary success is not proof of root cause. Re-enable the policy immediately and implement a narrowly scoped rule if the evidence supports one.
Rank #4
How to interpret common outcomes
| Observation | What it supports | What it does not prove |
|---|---|---|
| Browser opens BAM, BOINC cannot | A process-, proxy-, protocol-, or filtering difference is plausible. | That BAM, DNS, or the ISP is down. |
| Projects communicate, BAM fails | Project traffic and account-manager traffic may be treated differently. | That all outbound HTTP is allowed or that BAM is blocked server-side. |
| No firewall log entry for the retry | The request may be stopped before that device, sent through another proxy, or logged elsewhere. | That the client made no request. |
| Changing a rule makes the retry work | The changed path or policy is relevant and should be narrowed and documented. | That the temporary test alone identifies every contributing cause. |
When to escalate
If project traffic works but BAM contact still fails, send BOINC or BAM support the failing and working client versions, operating systems, endpoint values, complete account-manager messages, startup or client logs, and synchronized timestamps. State explicitly that browser access and project communication succeed while account-manager contact fails. BOINC’s official support routing directs software issues to its message boards or online help.
Do not omit the location comparison: it is more actionable than a generic connectivity error and helps support distinguish a client configuration problem from an outbound network-policy difference.
What remains unresolved
The historical report matching this symptom did not identify a confirmed root cause or verified fix. It also does not establish whether that network or BAM’s reachability from any particular ISP is the same today. Treat filtering, proxy handling, DNS, routing, and service availability as testable alternatives until timestamped client and network evidence separates them.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
