interactive dialog cannot call from interactive message button
when i post a json to url: http://<mattermost\_server>/api/v4/actions/dialogs/open

a dialog cannot open, the server log is below:

{"level":"debug","ts":1624384129.090824,"caller":"web/handlers.go:106","msg":"received http request","method":"post","url":"/api/v4/actions/dialogs/open","request\_id":"i…
i do not write go, but it seems like your

func(w http.responsewriter

should be similar to

responsewriter.header().set("content-type", "application/json")

responsewriter.writeheader(http.statusok)

jsondata := []byte(`{}`)

responsewriter.write(jsondata)
hey [@jsteb](/u/jsteb), i was struggling with this and i figured what is going on. the problem is with the action button. if you try with a regular button it will work. i think that should be clarified in the tutorial hi [@omar\_jandal](/u/omar_jandal) i found the problem!

somewhere on your site is a interaction fireing on your “article v3” class. [[image]](https://aws1.discourse-cdn.com/business5/uploads/webflow1/original/3x/e/f/ef1234ea647732bbbe8dcba17f1f3301d12dd79e.png "image") [[image]](https://aws1.discourse-cdn.com/business5/uploads/webflow1/original/3x/f/8/f8a0c96ba03678a653e0aa1af8c13d0e631a6558.png "image")

i don´t know where the interaction is set, but if you mind it i would simply change the color in the interaction from purple to green. or just delete it. i have also s… This is a public forum, not the link to Adobe support  
-other users here can't help with an account question  
Be sure to remain signed in with your Adobe ID before accessing the link below  
-you must also allow 'cookies' in your web browser for this to work  
<https://helpx.adobe.com/contact/support.html>  
-click the chat icon at the bottom right of the page to open a chat session  
-the chat icon looks like '3 dots inside a circle' at the lower right  
-type AGENT into the chat window to connect directly to a person rather than the AI  
Do be aware that Adobe's staffing is impacted by the virus, so wait times are long The problem is the response from the server, not your JavaScript. I ran the following code in the console on your page:



```
$.getJSON('data.json', function(data) { 
    console.log(data); 
});

        

        
        
        
 (adsbygoogle = window.adsbygoogle || []).push({});
 
        

    
```

The result looks like this:



  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

 ![enter image description here](https://fooobar.com//img/b0b4666ec951695a00da8c82eb85e737.jpg)


As you can see, there is only one property in the returned object ( `mesta`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

, an array with three elements).


You can confirm this by [visiting the file directly`data.json`
  




 (adsbygoogle = window.adsbygoogle || []).push({});](https://translate.googleusercontent.com/translate_c?depth=1&pto=aue&rurl=translate.google.com&sl=ru&sp=nmt4&tl=en&u=) . No other user in a public forum can help... and, since it does not seem that you are a plan administrator, I doubt that support can help


 


Be sure to remain signed in with your Adobe ID before accessing the link below  
-you must also allow 'cookies' in your web browser for this to work  
<https://helpx.adobe.com/contact/support.html> for chat or <https://helpx.adobe.com/contact/phone.html>  
-click the chat icon at the bottom right of the page to open a chat session  
-the chat icon looks like '3 dots inside a circle' at the lower right  
-type AGENT into the chat window to connect directly to a person rather than the AI  
Do be aware that Adobe's staffing is impacted by the virus, so wait times are long was caused because there was an "unhandled rejection error: eacces: permission denied, mkdir '/home//.npm/\_cache/index-<…>/

solved problem by just adding “sudo” in front

sudo npx create-react-app . i suspect that the resource\_exhausted message may have originated from a back-pressuring committer node ([code](https://github.com/digital-asset/daml/blob/926fb5997a795e7f80443a9a3ba7898b1568d158/ledger/participant-integration-api/src/main/scala/platform/apiserver/services/apisubmissionservice.scala#l155-l157)). if that’s the case, i believe the approach should be the same: change the configuration if you need and make sure to handle those errors with the appropriate retry strategy. the direct messaging icon doesn't appear until you have made your first post. you should be able to see it now. 
 
using 'direct messaging' before you have been asked to do so is considered a violation of the forum aup. see https://forums.xfinity.com/conversations/guidelines/xfinity-forum-acceptable-use-policy/602d9c64c5375f08cd574236. try checking if your mail server can actually be reached from your discourse server. easiest way to do that would be to run ./discourse-doctor

nb: what happens if you remove the smtp authentication string from the configuration and rebuild? i had to actually connect to the team viewer from remote to get this popup. can you please fix the documentation to reflect this step please?

https://community.teamviewer.com/t5/knowledge-base/how-to-control-a-mac-running-macos-10-14-or-higher/ta-p/44699#toc-hid--**please do not post teamviewer ids**