💾 Archived View for station.martinrue.com › jose › 2643456ff25a419594969e5d6ae0b1fb captured on 2024-06-16 at 13:31:21. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2024-05-10)
-=-=-=-=-=-=-
Being new to linux, and interacting with a linux server is like playing with knives. One slip up, and you make your gemini capsule inaccessible to the outside world. All I can do now is wait and hopefully someone will come along, with the right-sized band-aid, to fix my problem.
7 months ago · 👍 edanosborne
hi Jose... strange.. but at least you have a working system. That is a plus... · 7 months ago
Well, @fripster_ontour, I wasn't able to recreate the problem. I use the same system, the same editor, and the same file location. I tried to follow the same steps I had before, but everything worked out fine and my capsule was accessible, unlike before. Maybe I did something different before, but I don't know what that would have been. For all I know, it could have been cosmic rays affecting the server. · 7 months ago
oh that is good! normally you use the chmod command for changing that. Maybe the Windows sftp client did that… you could try to recreate the problem to be able to get to the bottom of your issue · 7 months ago
@fripster_ontour, No, but thank you. I was told I had inadvertantly changed my folder's permission to 700 . Changing it to 755 helped resolve my problem. What I can't understand is how I could've changed my folders permission settings. As, far as I can remember, all I did was connect to the server with sftp and used the put -R command to tranfer some files over. Bear with me, though. I'm just a newbie's noob to linux and all these file protocols, and who knows what I could have done to cause it. The files were transferred out of my Windows file structure, but I don't think that could've done anything. · 7 months ago
do you need help? · 7 months ago