Having a hard time connecting to Docker when running Test in Xcode

[jaysonng]

So I have an existing iOS project which I'm trying to run Tests on the new parse-server-swift docker setup I have running.

Everything seems to be ok with the Docker setup but when I run the Test on XCode, I get an error

error: ParseError code=141 error=connect ECONNREFUSED 127.0.0.1:8081

My setup is

/projects/MyProject
/projects/parse-server-swift

I've also set MyProject working directory to parse-server-swift trying to get it to connect.

When I access the url via localhost:8081/hello , the code works fine and I get a string back as expected.

What am I missing? Do I need to add a configuration somewhere that changes 127.0.0.1 to something else?

Full error

Test Case '-[LokalityTests.LocationTests testHelloVapor]' started.
2023-05-24 19:25:21.880953+0800 Lokality[48461:457393] [connection] nw_socket_handle_socket_event [C1.1.1:2] Socket SO_ERROR [61: Connection refused]

2023-05-24 19:25:21.887477+0800 Lokality[48461:457393] [connection] nw_socket_handle_socket_event [C2.1.1:2] Socket SO_ERROR [61: Connection refused]
error: ParseError code=141 error=connect ECONNREFUSED 127.0.0.1:8081

/Users/jayson/Projects/Lokality/Shared/LokalityTests/LocationTests.swift:459: error: -[LokalityTests.LocationTests testHelloVapor] : XCTAssertNil failed: "testHelloVapor failed"

Test Case '-[LokalityTests.LocationTests testHelloVapor]' failed (0.387 seconds).

Tests

struct TestHelloVapor: ParseCloudable {

        //: Return type of your Cloud Function
        typealias ReturnType = String

        //: These are required by `ParseCloudable`
        var functionJobName: String = "hello"

        //: Parameters

    }
    
    func testHelloVapor() async {
        let testHelloVapor = await TestHelloVapor()

        do {
            let string = try await testHelloVapor.runFunction()
            print("Lokality: \(string)")
        } catch {
            print("error: \(error.localizedDescription)")
            XCTAssertNil("testHelloVapor failed")
        }

    }

Having a headache trying to figure it out on my own.

[cbaker6]

I’m not sure I understand what you are trying to do. ParseServerSwift connects directly to your node Parse Server, your apps should not attempt to connect to ParseServerSwift directly, instead, your app should connect to your node Parse Server as it normally would. The Node JS server will forward Requests to ParseServerSwift when needed and let it handle cloud code function and trigger requests. This functions exactly how JS Cloud Code functions.

[jaysonng]

Thats what i figured. But for some reason I can't get my app to connect to the parseserverswift cloud function or maybe im not understanding the error im getting.

The econnrefused error I get means i have a configuration problem maybe?

error: ParseError code=141 error=connect ECONNREFUSED 127.0.0.1:8081

[cbaker6]

Your app should never connect to ParseServerSwift. ParseServerSwift should connect to your NodeJS ParseServer. Then your app should connect to your nodeJS Parse Server. Details about configuring are here: https://github.com/netreconlab/parse-server-swift#configure-parseserverswift-to-connect-to-your-parse-servers

[cbaker6]

I'm confident you've modified more than just PARSE_SERVER_DATABASE_URI which is different from what you've stated in #30 (reply in thread), as ECONNREFUSED 127.0.0.1:8081 doesn't make any sense for the original setup I've provided. This is probably due to you attempting to use the web hooks from XCTest and never removing them after.

From a docker standpoint, none of the code I provided would ever try communicate from a node Parse Server to ParseServerSwift through 127.0.0.1:8081. Even in the screenshots I provide, the web hooks show that node Parse Server communicates through http://cloud-code:8081 which will directly use the local network docker creates to reach ParseServerSwift. I also never bind to 127.0.0.1:8081 as this is 1) Unnecessary, 2) Unsafe due to ParseServerSwift containing the primaryKey of your server (you basically want minimize public access to anything that has the primaryKey, besides your node Parse Server). Your error states it's trying to communicate to a port that is never opened or binded to which is why your connection is refused (or, you are no longer your ParseServerSwift in Xcode).

You will need to provide the proper information in order for me to assist you in the future. You will also need to ensure you are using docker properly. If you make a change to ParseServerSwift, you need to:

1. Delete the current web hooks in your dashboard by clicking the trash can next to each hook. This is to ensure you always are using the latest hooks and not using the XCTest hooks you've been attempting to use in the past
2. In your terminal type, docker-compose stop cloud-code to stop the current container
3. In your terminal type, docker-compose build cloud-code to build the new container with your current changes
4. In your terminal type, docker-compose up -d cloud-code to start the recently built container

If you change something in docker-compose.yml, you need to:

1. In your terminal type, docker-compose restart parse cloud-code to restart the containers

[cbaker6]

If you update to 0.8.4 it will automatically delete the old hooks when you restart ParseServerSwift (in the linux container or Xcode) which will fix part of the issue I mentioned in #30 (reply in thread) as it seems like you are not deleting old hooks leftover from your XCTests. You should be sure to always verify the Destination column in the Webhooks section of your Parse Dashboard to ensure it's pointing to the correct ParseServerSwift endpoint you are testing/using

[jaysonng]

So I finally got it working when I finally pinpointed what that 127.0.0.1 error was.

Apparently my localhost isn't pointing to 127.0.0.1 ? Anyway, long story short,

http://localhost:8081 != http://127.0.0.1/8081 which for some reason is what node.js is using instead of localhost.

so in .env I changed PARSE_SERVER_SWIFT_HOST_NAME from localhost to 127.0.0.1 and got it playgrounds to work finally.

Docker setup also worked before this revelation where I didn't realize that I had to delete all triggers pointing to localhost. I thought i only needed to delete or change the hello webhook function I was testing. Your 0.8.4 update worked like a charm.

thanks @cbaker6, I can finally go about creating some Swift Cloud Code.

I'll just figure out the localhost not pointing to 127.0.0.1 problem or why Parse-Server node.js is looking for it next time.

[cbaker6]

So I finally got it working when I finally pinpointed what that 127.0.0.1 error was.

I'm glad you got your setup working!

I can finally go about creating some Swift Cloud Code.

You should be able to write Cloud Code fast since you are already familiar with ParseSwift. Definitely let me know if run into any bugs or features you feel are missing.

http://localhost:8081/ != http://127.0.0.1/8081 which for some reason is what node.js is using instead of localhost.

I've never seen localhost and 127.0.0.1 not be localhost, maybe your computer is force using IPv6 and not allowing IPv4 at all? https://www.lifewire.com/network-computer-special-ip-address-818385#toc-how-127001-works

[jaysonng]

I've never seen localhost and 127.0.0.1 not be localhost, maybe your computer is force using IPv6 and not allowing IPv4 at all? https://www.lifewire.com/network-computer-special-ip-address-818385#toc-how-127001-works

Right? I even checked /etc/hosts and it does say localhost is 127.0.0.1

Ill have to check on the link you sent in a couple of days.

Thanks again!

[cbaker6]

Sidenote: you can create a simple CloudCode function (similar to the HelloWorld example) to return "\(try await ParseServer.information())" to solve your the problem you posted: https://community.parseplatform.org/t/parse-server-version-property/3441/7