Hi, We are running MuleSoft On-Premise and I am trying to identify what the Antivirus Best Practise / Settings (e.g. exclusion paths etc.) are to ensure it doesn't impact the MuleSoft installation is anyone able to assist or point me in the right direction? Thank you Dave
,
Thank you for this information, I shall look at making the changes.
Dave
Hi, My mule application is deployed on cloudhub 2.0. When I am accessing the apis from postman I am getting the response but when users are caling thos apis from salesforce app, they are getting read time out and sometimes success as well. Sometimes the same issue happening from my postman as well. The imp thing is I am unable to see any logs in runtime manager for this read time out. Can anyone help me regarding this?
I am trying to log in in mulesoft
With the User and I am reciving below Error in anypoint studio :
org.mule.runtime.api.connection.ConnectionException: Failed establishing connection with salesforce
org.mule.runtime.api.connection.ConnectionException: Failed establishing connection with salesforce
Caused by: Invalid status code: 400, response body: {"error":"invalid_grant","error_description":"authentication failure"}
In Salesforce log history :
Username-Password Flow Disabled
for Basic connection type is Working fine
Outh User Name password it throwing above Erros
#MuleSoft
Hi Intkhab — this isn't a credential problem, it's the flow itself being turned off. Salesforce has disabled the OAuth 2.0 Username-Password flow by default (blocked in new orgs, being switched off in existing ones), and it's fully retired in Winter '27 — after which grant_type=password stops returning tokens. That's exactly your "Username-Password Flow Disabled" log entry plus the invalid_grant / authentication failure, even though the username, password, and token are correct.
Why your "Basic Authentication" connection still works: that MuleSoft connection type uses the SOAP login (username + password + security token), which is a different mechanism from the OAuth username-password flow — so it's unaffected. You can keep using Basic Auth as an immediate unblock today if you need one.
The proper fix is to move the Salesforce connector to a server-to-server OAuth flow:
- OAuth 2.0 JWT Bearer (recommended for MuleSoft to Salesforce): create a Connected App / External Client App with "Use digital signatures" (upload a certificate), pre-authorize the app for the integration user's profile or permission set, then in the connector switch the connection to OAuth JWT Bearer and supply the consumer key, the username, and the private key/keystore. No password stored.
- OAuth Client Credentials is the other supported option — a connected app with client credentials enabled and a Run-As integration user.
In the Anypoint Salesforce connector you change the connection type from "Username Password" to "OAuth JWT Bearer" (or Client Credentials) and remove the stored password.
If you specifically need the old flow back short-term, an admin can check Setup - Identity - OAuth and OpenID Connect Settings for "Allow OAuth Username-Password Flows" — but that toggle is going away with the Winter '27 retirement, so treat it as a stopgap, not a fix. JWT Bearer is the durable path.
Ref: OAuth 2.0 JWT Bearer Flow for Server-to-Server Integration:
https://help.salesforce.com/s/articleView?id=sf.remoteaccess_oauth_jwt_flow.htm&type=5I am trying to deploy training4-american-ws (from mulesoft training) app to cloudhub 2.0 using anypoint studio, and while on Wi-Fi i always get this error:
Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:3.1.4:deploy (default-deploy) on project training4-american-ws: Failed to deploy artifacts: Could not transfer artifact c4a3bb0a-a224-4d98-8ed2-d888355c80db:training4-american-ws:jar:mule-application:1.0.0 from/to anypoint-exchange-v3 (
https://maven.anypoint.mulesoft.com/api/v3/organizations/c4a3bb0a-a224-4d98-8ed2-d888355c80db/maven/runId/d90b03c8-e643-4554-8f56-c257c2ca780b): status code: 500, reason phrase: Internal Server Error (500) -> [Help 1]
, however when i am on cable internet i am able to deploy successfully.
Why it won't deploy using Wi-Fi, and is there any fix for this?
Happy to hear that now it's working. Although it's a really weird behaviour.
But now it's clear the issue is on AnypointStudio network settings, try to have a look there, just in case there is something misconfigured.
Best
Has anyone faced such issue?
I created a custom policy using the maven archetype. Deployed the policy to exchange.
In exchange i can see the new custom policy.
When i go to API Manager, i am able to see the custom Policy inside the Automated Policies Section. But the custom policy is NOT VISIBLE under API Level Policies.
Im using a developer trial account, below is my custom policy zip file
I would like to enable or disable an HTTP proxy dynamically based on a YAML property.
service:
useHttpProxy: "true"
HTTP Request Config:<http:request-config name="service-config">
<http:request-connection
protocol="HTTPS"
host="${service.host}"
port="${service.port}"
proxyConfig="#[
if (Mule::p('service.useHttpProxy') == 'true')
'proxyConfig'
else
null
]" />
</http:request-config><http:proxy
name="proxyConfig"
host="${proxy.host}"
port="${proxy.port}" />
I get the following error:
Unable to convert 'proxyConfig' with class 'java.lang.String'
to class 'HttpProxyConfig'
WriterExecutionException:
Unable to convert 'proxyConfig' with class 'java.lang.String'
to class 'HttpProxyConfig'
My understanding is that the proxyConfig attribute expects an HttpProxyConfig object, while my expression returns a String ("proxyConfig").
Is it possible to dynamically set the proxyConfig attribute using a DataWeave expression? Because I don't like to have two separate http:request-config definitions (one with a proxy and one without) and select the appropriate one at runtime
Thank you in advance!
#MuleSoft
this way works if(Mule::p('phoenix-sys.useHttpProxy') == "true")
app.registry.proxyConfig //or app.registry['proxyConfig']
In database select connector
I prepare sql and input param correctly as below shown, it works at runtime as well
but IDE always gives me error as below, which is annoying, how to get rid of this IDE error?
Thank you all in advance
#MuleSoft
Forum Ambassador
Hello,
I would not prefer to go for a query builder inside the variable rather I would use an Input parameter with Dynamic binding in the connector itself.
If you really want to get rid of then you can use like below , but that is not ideal solution .
#[vars.query default "some default DB query you can write here"]
Thanks Sai and Manish (Key was working fine with Mule agent as well as from open ai postman collection), you both are right. but main issues were the error response misleading the meaning of troubleshooting (Authentication failed means 401 while creating the LLM proxy
). I discussed with Salesforce team (Shubham), Now he will reach out to technical team for more descriptive response will come.
Below is response from Salesforce.
"Feedback was raised regarding the need for more descriptive, user-friendly error messages that clearly indicate when an error is subscription-related, to improve the troubleshooting experience."
Added system args in launch.json , able to see them in output console but when deploying it getting couldn't find the property.
added -Dmule.env=Dev able to see it in output console, but getting couldn't find ${mule.env} while debug/run in VS Code.
Anything am missing here?
Forum Ambassador
Hello,
For ACB, You can try below and let me know in comment section.
1. For Lauch.json file, use below for windows machine.
"windows": {"mule.runtime.args": "${config:mule.runtime.defaultArguments} -M-Denv=Dev" }2. Or Use your same solution if it works with -M-Denv=Dev else use option 1 .
3. Open Setting in ACB and set indefault Argument like below:
Thanks,
Manish Kumar Yadav
Trailblazer Community Forum Ambassadors
Hi everyone,
we’re facing an issue after migrating our MuleSoft Runtime Fabric (RTF) installation from Ubuntu 22 to Ubuntu 24 VMs. RTF itself installs the resource-cache application, which runs an nginx container. The nginx config (nginx.conf, from ConfigMap resource-cache-config) includes:
listen [::]:8010 default_server;
This enables an IPv6 listener.
On Ubuntu 22 (with IPv6 enabled), this worked fine. But Ubuntu 24 has IPv6 disabled, so the nginx container can’t start, leading to pod deployment failures.
Every time we update the ConfigMap (e.g., with a helm update or during pod moves), the IPv6 listener directive comes back, requiring manual editing. We don’t have a permanent solution.
Questions:
Currently we work around it by manually editing the ConfigMap. Any best practice or official guidance would be appreciated!
Thanks in advance.
Hi all,
following up on the question of disabling the IPv6 listener for RTF’s NGINX (listen [::]:8010
) on Ubuntu 24, I received this official response from MuleSoft Support:
Thanks for all the support and responses.
Best regards,
Denny