![image.png](https://cdn.steemitimages.com/DQmdsK4R8hW6QQSwVB1zYd5DCv1MhpBRdekAYqvGnJqgpdR/image.png)

2 days ago we started fiddling with steemconnet to port it to weku.
Some 18 compounded hours afterwards there is progress...

After what looked like a easy job of changing nodes and providing the proper chain id and prefix and we had a landing steemconnect page in our server we tought it was just a matter of now replacing the interface to change steem by weku...

**Surprise!**
It is not that easy, when calling the API node we are getting blocked by CORS policy and trying to send the adequate headers becomes a puzzle.

* On using http:// and port we get a 400 error **Bad request**
* On using http:// with no port to call the API node we get a 301 error **Moved permanently**
* On using https://with no port to call the API node we get a 502 error **Bad Gateway**

**Still working on it...**
Hopefully we will discover where it is breaking, it is steemconnect?, is it the security of the RPC node?, Is it our code ?

A hint is that before modifying the dsteem that comes with steem connect we had a page, but dsteem was connecting to steemit not weku. (actually was connecting two both)

**... Dont miss the next chapter**
Hopefully will be an announceent

*****
*****

<center>**[First published in weku.io](https://main.weku.io/community-deals/@nnnarvaez/code-blog-weku-connect-is-it-possible-codename-wekuaccess).**</center>