[google-appengine] Re: Compute Engine Instances Hidden/Erased

['Mohammad I (Cloud Platform Support)' via Google App Engine]

Hello Dmitri, 

The issue of Compute Engine Instances hidden/deleted that you have reported 
seems related to Compute Engine not Google App Engine. 

I would recommend you to create a Compute Engine Issue under the “Compute” 
section by going here 
 as the 
issue may be required to refer to the Cloud Engine Engineering team to 
resolve it. Please select the private component as probably you will have 
to share project specific information, so that it is not visible to the 
public. One of the Google Cloud Platform Support Agents will assist you to 
resolve your issue.

Please note that Google Groups 
 
is only meant for general discussion related to Google Cloud Platform 
products which are not technical in nature, service status updates and 
release notes, and ranging from book recommendations to creative shortcuts.

Just for your information this document 
 
provides information on how to restore a persistent disk from snapshot. 


On Wednesday, August 26, 2020 at 2:10:44 PM UTC-4 Dmitri Love wrote:

> It appears that all of our compute engines have been erased, we have very 
> crucial data for our business infrastructure, and without this our company 
> dies. Can someone help me restore these in my cloud console?

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/1ac33a8b-1cc5-401e-b72a-8e66463631fan%40googlegroups.com.

[google-appengine] Re: Google BLOB service stopped to upload files in US region,

['Mary (Google Cloud Support)' via Google App Engine]

Hello, 

There was a service interruption with BlobStore on the 21st which was 
resolved. If you are still experiencing issues, we recommend to open a 
support ticket via the Support Hub[1] to further investigate into your 
issue. 


[1] https://cloud.google.com/support-hub/

On Friday, August 21, 2020 at 5:08:02 PM UTC-4 Jason Li wrote:

> Is it possible to let us know if this BlobStore upload issue will be 
> fixed?  Thanks!
>
> On Friday, August 21, 2020 at 3:50:36 AM UTC-5 Jason Li wrote:
>
>> It looks like BlobStore upload is still broken. We use Python 2.7 and 
>> here is the boilerplate code used in our system:
>>
>> class MainHandler(webapp2.RequestHandler):
>>
>>   def getUploadForm(self):
>> upload_url = blobstore.create_upload_url('/imageUpload')
>>
>> self.response.write('\n\n')
>> self.response.write('> enctype="multipart/form-data">\n'% upload_url)
>> self.response.write('> accept=".png">\n')
>> self.response.write('> value="Submit">\n')
>> self.response.write('\n\n\n')
>>   .
>>
>> After the user hits the Submit button, a 500 error will be returned. The 
>> expected behavior is that the image will be uploaded to BlobStore and then 
>> navigate to myDomain.com/imageUpload. Note that the 500 error occurred 
>> before navigating to image upload success handler myDomain.com/imageUpload. 
>> Because the issue is not on our codebase, we cannot see any errors/traces 
>> on Google Cloud Console/App Engine Dashboard.
>>
>> The same code has worked for at least 5 years.  We understand that we 
>> need to move to Google Cloud Storage and switch to Python 3, but we have a 
>> complex system and it will be a huge undertaking for us. I really hope 
>> Google can fix this issue as soon as possible. Thanks!!
>> 
>>
>>1. Request URL: 
>>   
>>   
>> https://www.mydomain.com/_ah/upload/AMmfu6axah0bzR6QPuVaEb1I3WnGVpuSAU11QSdFFGLWFl15YMvLUJEqN6lZZw_RxH6pQp7TOORbPEApZe4OZNnreTAjLNiYuKgp0AGlghpIZ_iYtUDLmKSSO11lTEecdu_sFcQV3n7qsPZ28OWss_NVN6c5CA2p794poyCYpBWiLBarvdCksLtKJJA0IUiuNcyJQRD6FmDPHonHngD0d8FImpWqa6_XNA/ALBNUaYAXz85bB_Pf7F0dGmJhgGZNsyQ9RN_d5lv/
>>   2. Request Method: 
>>   POST
>>   3. Status Code: 
>>   500 
>>   4. Remote Address: 
>>   [2607:f8b0:4000:816::2013]:443
>>   5. Referrer Policy: 
>>   no-referrer-when-downgrade
>>   1. Response Headers
>>   1. content-length: 
>>   0
>>   2. content-type: 
>>   text/html; charset=UTF-8
>>   3. date: 
>>   Fri, 21 Aug 2020 02:53:14 GMT
>>   4. server: 
>>   UploadServer
>>   5. status: 
>>   500
>>   6. x-guploader-uploadid: 
>>   
>>   
>> AAANsUkAqnyXebkSBTKiYHZ4ObP9rk0weOQ1jiBRXpkDQhdc73HeJydQvAIR6_bl-Z-VG-QWfWqDMe4FP3ErHqdYMObvuyA44A
>>   2. Request Headers
>>   1. :authority: 
>>   www.mydomain.com
>>   2. :method: 
>>   POST
>>   3. :path: 
>>   
>>   
>> /_ah/upload/AMmfu6axah0bzR6QPuVaEb1I3WnGVpuSAU11QSdFFGLWFl15YMvLUJEqN6lZZw_RxH6pQp7TOORbPEApZe4OZNnreTAjLNiYuKgp0AGlghpIZ_iYtUDLmKSSO11lTEecdu_sFcQV3n7qsPZ28OWss_NVN6c5CA2p794poyCYpBWiLBarvdCksLtKJJA0IUiuNcyJQRD6FmDPHonHngD0d8FImpWqa6_XNA/ALBNUaYAXz85bB_Pf7F0dGmJhgGZNsyQ9RN_d5lv/
>>   4. :scheme: 
>>   https
>>   5. accept: 
>>   
>>   
>> text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9
>>   6. accept-encoding: 
>>   gzip, deflate, br
>>   7. accept-language: 
>>   en-US,en;q=0.9
>>   8. cache-control: 
>>   max-age=0
>>   9. content-length: 
>>   205103
>>   10. content-type: 
>>   multipart/form-data; 
>>   boundary=WebKitFormBoundaryyCwtZU7W4GyPos5l
>>   11. cookie: 
>>   
>> __utmz=157282283.1597952850.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=(not%20provided);
>>  
>>   
>> __gads=ID=53591dab302103ee:T=1597952850:S=ALNI_MaF4YdKpIKyFr4pSlgJeMJlFfmocQ;
>>  
>>   __utmc=157282283; 
>>   __utma=157282283.1009616170.1597952850.1597965252.1597975354.3; 
>> __utmt=1; 
>>   __utmb=157282283.9.10.1597975354
>>   12. origin: 
>>   https://www.mydomain.com
>>   13. referer: 
>>   https://www.mydomain.com/mypage.html
>>   14. sec-fetch-dest: 
>>   iframe
>>   15. sec-fetch-mode: 
>>   navigate
>>   16. sec-fetch-site: 
>>   same-origin
>>   17. sec-fetch-user: 
>>   ?1
>>   18. upgrade-insecure-requests: 
>>   1
>>   19. 
>>   user-agent: 
>>   Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 
>>   (KHTML, like Gecko) Chrome/84.0.4147.135 Safari/537.36
>>   20. 
>>   
>> On Thursday, August 20, 2020 at 4:49:30 PM UTC-5 henry@gmail.com 
>> wrote:
>>
>>> Do you want to say the analyst managed to upload an image to the BLOB? 
>>> Please provide an URL to this BLOB please?
>>>
>>>
>>> On Thursday, August 20, 2020 at 2:21:17 p.m. UTC-7 Elliott

Re: [google-appengine] Spending LImits Going Away :(

['yananc' via Google App Engine]

Hello Joshua,

The budget alert will be triggered once your costs rise above the threshold 
you specify. However, as Alexis has explained, there are various factors 
that might affect ‘how quickly’ you will receive the alert.

Same as the email you shared, the documentation [1] provides details on how 
to manage App Engine costs. Specifically, besides mechanisms such as 
setting the max number of instances, Budget Alerts, Pub/Sub, and Cloud 
Functions could be used to automatically disable your app when your costs 
exceed the threshold you specify. The documentation also provides steps on 
how to implement it with sample codes.

Back to the issue of ‘Cloud Datastore Read Operations’ being too high, a 
possible solution is to leverage cache mechanism to avoid excessive 
operations. You may find more information from the topic [2].

Hope it helps.

[1]: https://cloud.google.com/appengine/docs/managing-costs

[2]: 
https://stackoverflow.com/questions/12939376/google-app-engine-too-many-datastore-read-operations

On Tuesday, August 25, 2020 at 6:51:49 PM UTC-4 Luca de Alfaro wrote:

> Yes, at least, we can hard limit the number of active instances: see 
> https://cloud.google.com/appengine/docs/standard/python3/config/appref
> So if every active instance has a limited rate of use of backend services 
> (like datastore), and there are no services accessible except via an 
> appengine instance (e.g., no GCS direct bandwidth), in practice we can put 
> a bound using that. 
>
> Luca
>
> On Tue, Aug 25, 2020 at 3:45 PM Luca de Alfaro  wrote:
>
>> I concur with the worry.  Is there any _technical_ reason why it is a 
>> good idea to do away with a spending limit?  Can we get an instance limit 
>> instead? 
>> This is suddenly making standard non-scalable systems on AWS look better 
>> than appengine! 
>>
>> On Tue, Aug 25, 2020 at 9:03 AM Joshua Smith  
>> wrote:
>>
>>> Once again last night, my wallet was saved when a runaway bot chewed up 
>>> my site’s whole daily spending limit. I got an email from a user, set up a 
>>> firewall rule, and goosed my budget to get things going again.
>>>
>>> I’m *very* concerned about Google’s decision to remove this feature. 
>>> Offering a cloud service that bills by usage without having a way to limit 
>>> the spend shifts an unreasonable amount of risk onto the subscriber.
>>>
>>> I’ve set up budget alerts, as suggested, but I’m concerned that:
>>>
>>> - What if my bill shoots up really fast? How quickly is this alert going 
>>> to go out?
>>>
>>> - What if I am away from the computer (remember when we used to be able 
>>> to leave our houses? good times… good times…)?
>>>
>>> I run this particular site as a not-for-profit social good. (It’s a site 
>>> that small town governments use to post their meetings.) I make *no* money 
>>> on it.
>>>
>>> I’d be perfectly happy to handle this with self-set quotas on something 
>>> other than dollars. For example, in my case the budget-buster is always 
>>> “Cloud Datastore Read Operations.” If I could set a cap on that one thing, 
>>> it’d give me the protection I need.
>>>
>>> -Joshua
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Google App Engine" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to google-appengi...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/google-appengine/FC0F0C74-0D40-48DF-8919-208202A9B1A8%40gmail.com
>>>  
>>> 
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/79fa52cd-f974-42af-8706-eac3e1409123n%40googlegroups.com.

[google-appengine] Re: How to cut my GCP Load Balancer costs

['Anurag Sharma' via Google App Engine]

Hello

You are being charged for HTTP Load Balancing: Global Forwarding Rule 
Minimum Service Charge, for which the pricing is calculated at 0.025 USD 
per hour [1]. The way out of this is to reconsider the number of Global 
forwarding rules that you are using [2]

[1]: 
https://cloud.google.com/skus/?currency=USD&filter=HTTP+Load+Balancing%3A+Global+Forwarding+Rule+Minimum+Service+Charge
[2]: https://cloud.google.com/load-balancing/docs/forwarding-rule-concepts

On Wednesday, August 26, 2020 at 4:14:34 AM UTC-4 xun...@gmail.com wrote:

> Hi, 
> here I have many apps, I create GCP project for each app. I use Google 
> Storage as app's resource backend. To accelerate request speed, I also use 
> Google CDN. So in each project, I create one https load balancer using 
> storage as backend and open CDN function. 
>
> Everything goes on well, but recently, I find every project will be 
> charged on `HTTP Load Balancing: Global Forwarding Rule Minimum Service 
> Charge`, almost 18 USD per project, really so expensive to me, any good 
> suggestion for me to cut the costs? Thanks a million.
>
>
> [image: Screen Shot 2020-08-26 at 12.04.34 PM.png]
>
> [image: Screen Shot 2020-08-26 at 12.05.41 PM.png]
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/00094bf8-ff19-474d-9278-4fb018374b77n%40googlegroups.com.

[google-appengine] Please share article to set load balancer for GAE

[Arun Gopi]

Hi, Need to set up load balance for public facing app. can you please 
provide me the doc to set up load balancer for GAE?

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/0f9a2a4b-6f80-4118-9e9b-4d899f551bb2n%40googlegroups.com.

[google-appengine] Re: How to use Cloud Armor with GAE Flex?

[Arun Gopi]

Our application is a public facing app deployed on GAE standard. we cannot 
have firewalls or IAP so in our case we are left with cloud load balancer 
to mitigate DDOS.

can you please share document for load balancer for GAE? also for cloud 
aromor for our use case

On Friday, May 29, 2020 at 9:10:18 AM UTC-4 Olu wrote:

> For any feature or Nice-to-have features that you would like to see 
> implemented on the Google Cloud Platform or Google App Engine, you can 
> always submit a feature request with detailed information about such 
> features on the GCP issues tracking tool[1][2]. This would be evaluated and 
> considered, should it fit into the long term plan or road map of the Google 
> Cloud Platform.  
>
> Please keep in mind though that feature requests are subject to the 
> evaluation of the particular Product team and there are no ETA for the 
> implementation of such feature requests.
>
> Particularly about using Cloud Armor with the Google App Engine, there is 
> already a feature request open about this request and it is currently being 
> evaluated by the App Engine team. I recommend that you bookmark the link to 
> receive regular updates about the feature. 
>
> Thank you. 
>
> [1]https://developers.google.com/issue-tracker/#public_users
> [2]https://issuetracker.google.com
> [3]https://issuetracker.google.com/144150754
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/6d2e08be-765e-45aa-83d5-a82ea9990752n%40googlegroups.com.

[google-appengine] Re: The requested URL / was not found on this server in Google App Engine for Vue .js

['Aditya' via Google App Engine]

The error message indicates that the specified URL is invalid. Please check 
the value assigned for 'url' in main.py and assign it to app.yaml. 

On Tuesday, August 25, 2020 at 12:41:54 PM UTC-4 niraj...@gmail.com wrote:

> I have deployed code in Google app engine server with route mode changes 
> from mode: 'hash' to mode: 'history'. After this change, I am getting this 
> error.
>
> Error: Not Found The requested URL /login was not found on this server.
>
> Here is app.yaml
> runtime: python27 
> api_version: 1 
> threadsafe: true 
>  handlers:
>  - url: / 
>  static_files: index.html 
>  upload: index.html 
>
>  - url: /(.*) 
>  static_files: \1 
>  upload: (.*) 
>
> Can anybody please help me...
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/c7282482-16f9-4584-870f-f821d9f242e2n%40googlegroups.com.

Re: [google-appengine] Spending LImits Going Away :(

['yananc' via Google App Engine]

*Hello Joshua,The budget alert will be triggered once your costs rise above 
the threshold you specify. However, as Alexis has explained, there are 
various factors that might affect ‘how quickly’ you will receive the 
alert.Same as the email you shared, the documentation [1] provides details 
on how to manage App Engine costs. Specifically, besides mechanisms such as 
setting the max number of instances, Budget Alerts, Pub/Sub, and Cloud 
Functions could be used to automatically disable your app when your costs 
exceed the threshold you specify. The documentation also provides steps on 
how to implement it with sample codes.Back to the issue of ‘Cloud Datastore 
Read Operations’ being too high, a possible solution is to leverage cache 
mechanism to avoid excessive operations. You may find more information from 
the topic [2].Hope it helps.[1]: 
https://cloud.google.com/appengine/docs/managing-costs 
[2]: 
https://stackoverflow.com/questions/12939376/google-app-engine-too-many-datastore-read-operations
 
*

On Tuesday, August 25, 2020 at 6:51:49 PM UTC-4 Luca de Alfaro wrote:

> Yes, at least, we can hard limit the number of active instances: see 
> https://cloud.google.com/appengine/docs/standard/python3/config/appref
> So if every active instance has a limited rate of use of backend services 
> (like datastore), and there are no services accessible except via an 
> appengine instance (e.g., no GCS direct bandwidth), in practice we can put 
> a bound using that. 
>
> Luca
>
> On Tue, Aug 25, 2020 at 3:45 PM Luca de Alfaro  wrote:
>
>> I concur with the worry.  Is there any _technical_ reason why it is a 
>> good idea to do away with a spending limit?  Can we get an instance limit 
>> instead? 
>> This is suddenly making standard non-scalable systems on AWS look better 
>> than appengine! 
>>
>> On Tue, Aug 25, 2020 at 9:03 AM Joshua Smith  
>> wrote:
>>
>>> Once again last night, my wallet was saved when a runaway bot chewed up 
>>> my site’s whole daily spending limit. I got an email from a user, set up a 
>>> firewall rule, and goosed my budget to get things going again.
>>>
>>> I’m *very* concerned about Google’s decision to remove this feature. 
>>> Offering a cloud service that bills by usage without having a way to limit 
>>> the spend shifts an unreasonable amount of risk onto the subscriber.
>>>
>>> I’ve set up budget alerts, as suggested, but I’m concerned that:
>>>
>>> - What if my bill shoots up really fast? How quickly is this alert going 
>>> to go out?
>>>
>>> - What if I am away from the computer (remember when we used to be able 
>>> to leave our houses? good times… good times…)?
>>>
>>> I run this particular site as a not-for-profit social good. (It’s a site 
>>> that small town governments use to post their meetings.) I make *no* money 
>>> on it.
>>>
>>> I’d be perfectly happy to handle this with self-set quotas on something 
>>> other than dollars. For example, in my case the budget-buster is always 
>>> “Cloud Datastore Read Operations.” If I could set a cap on that one thing, 
>>> it’d give me the protection I need.
>>>
>>> -Joshua
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Google App Engine" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to google-appengi...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/google-appengine/FC0F0C74-0D40-48DF-8919-208202A9B1A8%40gmail.com
>>>  
>>> 
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b225afc2-640e-40e8-afb9-9a672b4a8b55n%40googlegroups.com.

Re: [google-appengine] "Google Cloud API" was not in in "Adding credentials to the project".

['Mary (Google Cloud Support)' via Google App Engine]

Hello, 

Can you please provide additional information in order for us to assist 
you. Which API are you attempting to enable? When adding credentials are 
you referring to OAuth or are you referring to IAM credentials for service 
accounts? 
On Saturday, August 22, 2020 at 9:54:19 PM UTC-4 Wesley C (Google) wrote:

> This is the Google App Engine mailing list. To use the PaaS system, you 
> only need to create a project (which you have already done) then go to 
> console.cloud.google.com/appengine to create your App Engine app. There's 
> no need to create credentials or use a "Google Cloud API" unless you know 
> you need to do so. I suggest installing the Google Cloud SDK (
> cloud.google.com/sdk) which provides tools to simplify creating & 
> deploying your app. To learn more about App Engine, please see 
> cloud.google.com/appengine for its documentation. If you have any 
> specific questions, feel free to ask here but paste any specific commands 
> or screenshots showing where you may have an issue.
>
> Good luck!
> --Wesley
>
> On Sat, Aug 22, 2020 at 11:53 AM I snb  wrote:
>
>> In the console of Google cloud platform, I created project name -> Google 
>> cloud API -> Credentials. However, "Google Cloud API" was not an option in 
>> "Adding credentials to the project".
>
>  
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> "A computer never does what you want... only what you tell it."
> wesley chun :: @wescpy  :: Software 
> Architect & Engineer
> Developer Advocate at Google Cloud by day; at night...
> Python training & consulting : http://CyberwebConsulting.com
> "Core Python" books : http://CorePython.com
> Python blog: http://wescpy.blogspot.com
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/0038ac64-361c-4380-9e82-fce635c13b20n%40googlegroups.com.

[google-appengine] Re: Deploying to App Engine Standard Env + Laravel Project + Read-only file system error

['Alexis (Google Cloud Platform Support)' via Google App Engine]

Hi Hadil,

The error says: "Failed to open stream: Read-only file system". I think 
this means that it's finding a file there already (under 
"/workspace/storage/framework/views/") where it shouldn't be. This could be 
a caching issue with Laravel where the files are upload by certain machines 
only. However, if it isn't a caching issue, then something is different 
about those local machines and what it uploads since one dev doesn't have 
this problem 100% of the time. It could also be a config issue in Laravel.

Scenario 1: If all the devs are pulling from the same repo:
- What if you try one of these[1] commands to clear view cache on 
non-working machines?
- What if you try clearing the general[2] cache on non-working machines?
- Check the gitignore file if it's the same across stations that work and 
don't work

Scenario 2: If the devs are not pulling from same repo:
- Where is the part of the code that should have VIEW_COMPILED_PATH? Is 
that code different across repos?
- Check the gitignore file if it's the same across stations that work and 
don't work

There's a lot of possibilities, but I suspect it might be caching being 
uploaded into the wrong path somehow. Probably due to local testing.

[1] https://laravel.com/docs/7.x/views#optimizing-views
[2] https://laravel.com/docs/7.x/configuration#configuration-caching

On Wednesday, August 26, 2020 at 4:16:05 AM UTC-4 hadil.cha...@mmpww.com 
wrote:

> Hello Mary,
>
> Thank you for your reply.
>
> The app.yaml file already includes "/*tmp*" for both "*VIEW_COMPILED_PATH*" 
> and "*APP_STORAGE*". For more permanent files, we're already using Cloud 
> Buckets. What Laravel is trying to do is store compiled views (which are 
> *temporary* files) onto "/*workspace*/storage/framework/views/". However, 
> from app.yaml we already set "VIEW_COMPILED_PATH" as *tmp*, why is the 
> code still trying to save onto the "*workspace*" directory? I need to 
> emphasize again that this project has been working fine for more than a 
> year on app engine and it started breaking only 2 weeks ago. I appreciate 
> the links you shared but if you read the problem carefully you'll see that 
> the links do not address our issue.
>
> With the above in mind, can you please direct us towards a solution?
>
> On Wednesday, August 26, 2020 at 12:13:31 AM UTC+3 Mary (Google Cloud 
> Support) wrote:
>
>> Hello Hadil,
>>
>> Yes that is correct. Since App Engine Standard the disk is read-only[1] 
>> with the exception of the /tmp directory, the app.yaml file will be need 
>> modified for the APP_STORAGE to reflect /tmp  as you have mentioned. If 
>> these are static files that Laravel needs to retrieve you can use a Cloud 
>> Storage bucket to store them. There is an open source Laravel Google Cloud 
>> Storage Package[2] which can help you with this. More information can be 
>> found on how to configure Laravel with the above package[3]. Please be 
>> aware since this package is open source, it is not supported or endorsed by 
>> GCP.
>>
>> [1] 
>> https://cloud.google.com/appengine/docs/the-appengine-environments#comparing_high-level_features
>> [2] https://github.com/Superbalist/laravel-google-cloud-storage
>> [3] 
>> https://stackoverflow.com/questions/57177524/laravel-how-to-access-stored-image-from-google-cloud-storage-using-php-laravel
>>
>> On Tuesday, August 25, 2020 at 8:02:02 AM UTC-4 hadil.cha...@mmpww.com 
>> wrote:
>>
>>> Also, something else worth noting is that we're not sure why Laravel is 
>>> trying to the write to the folder "/*workspace*/storage/framework/views/" 
>>> instead of "/*tmp*/storage/framework/views/". Also, in case it's 
>>> helpful to someone, below is a copy of our app.yaml (it's been configured 
>>> the same way for over a year):
>>>
>>> APP_KEY: XXX
>>> APP_URL: 'X'
>>> APP_NAME: XXX
>>> APP_STORAGE: /tmp
>>> APP_ENV: production
>>> APP_DEBUG: true
>>> VIEW_COMPILED_PATH: /tmp
>>>
>>> On Monday, August 24, 2020 at 7:02:51 PM UTC+3 Hadil Charafeddine wrote:
>>>
 Hello,

 Our team has been using App Engine Standard for this project (PHP and 
 Laravel 5.8.38) for over a year now without any issues with deployment. 
 However, a couple of weeks ago we started getting a 500 HTTP error every 
 time we deploy (with and without --no-promote option).

 When we check our logs, we find that the error is caused by:
 *2020/08/18 06:15:15 [error] 25#25: *2 FastCGI sent in stderr: "PHP 
 message: PHP Fatal error:  Uncaught ErrorException: 
 file_put_contents(/workspace/storage/framework/views/c1b305dfa33e081e1fc836f46439e09f829e8770.php):
  
 failed to open stream: Read-only file system*

 It's very weird that we're receiving this message now even though the 
 project has been working fine for more than a year and we've made 
 countless 
 deployments to date without this issue. Furthermore, we did not update the 
 configuration of the project nor did we update the Laravel version.

[google-appengine] Compute Engine Instances Hidden/Erased

[Dmitri Love]

It appears that all of our compute engines have been erased, we have very 
crucial data for our business infrastructure, and without this our company 
dies. Can someone help me restore these in my cloud console?

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b13b63f6-83ca-4586-9b6f-f7cabdc274e6n%40googlegroups.com.

[google-appengine] Re: Getting an error in the php zip module

[Suhendar Aryadi]

Hello,

Yes, I really use that service. When deploying the instance I got no 
errors. 
While installing the theme I get an error notification as listed in the 
post above.

Pada Rabu, 26 Agustus 2020 pukul 02.33.29 UTC+7 amit...@google.com menulis:

> Hello,
>
> To clarify, could you please confirm if you use this [1] service to deploy 
> the Wordpress? Also please let us know if you are getting this error while 
> deploying the instance?
>
> [1] https://cloud.google.com/wordpress
>
> On Tuesday, August 25, 2020 at 3:37:31 AM UTC-4 suhenda...@gmail.com 
> wrote:
>
>> Thanks for your attentions
>>
>> I use Google Cloud Compute with instances installed in wordpress. 
>> I have also read that the php zip module is already active on GCP. But I 
>> have tried on several wordpress themes. The notification is the same. 
>>
>> "ZipArchive Support: No ZipArchive is required for plugins installation 
>> and pre-made websites import. Please contact your hosting provider."
>> Pada Selasa, 25 Agustus 2020 pukul 01.38.23 UTC+7 David (Cloud Platform 
>> Support) menulis:
>>
>>> Could you specify if you are using App Engine standard or flexible?
>>> Zip should be enabled by default in both App Engine Standard 
>>> 
>>>  
>>> and Flexible 
>>> .
>>>   
>>> However, if you believe this is a Wordpress specific issue, you may benefit 
>>> from asking this within the Wordpress Community Forums 
>>> .
>>> On Saturday, August 22, 2020 at 2:53:58 PM UTC-4 suhenda...@gmail.com 
>>> wrote:
>>>
 Hi,

 Firstly can I thank you for offering this community support - it's 
 invaluable.

 My question is how to enable the php zip module on php runtime?

 Many thanks in advance for your help.

 Suhendar

>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/18b2eb26-acd3-4e3a-8221-c48a2d2d2580n%40googlegroups.com.

[google-appengine] Wordpress + Google domain

[Irinel Panacci]

Hi,
I created WordPress on google cloud. It works properly. Statito IP set. 
Created my zone with all www and not IP addresses. I changed the NS of my 
domain on google pointing them to those of google cloud.
Did I do everything right? Will the SSL certificate be issued automatically 
since my domain is registered on Google domains or not? How do I change the 
address within WordPress? Thank you. Is the procedure I have done correct?

(Sorry for my English)

Irinel

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b9aa2721-e50d-4a39-bcf7-c074265f9069n%40googlegroups.com.

[google-appengine] Re: Deploying to App Engine Standard Env + Laravel Project + Read-only file system error

[Hadil Charafeddine]

Hello Mary,

Thank you for your reply.

The app.yaml file already includes "/*tmp*" for both "*VIEW_COMPILED_PATH*" 
and "*APP_STORAGE*". For more permanent files, we're already using Cloud 
Buckets. What Laravel is trying to do is store compiled views (which are 
*temporary* files) onto "/*workspace*/storage/framework/views/". However, 
from app.yaml we already set "VIEW_COMPILED_PATH" as *tmp*, why is the code 
still trying to save onto the "*workspace*" directory? I need to emphasize 
again that this project has been working fine for more than a year on app 
engine and it started breaking only 2 weeks ago. I appreciate the links you 
shared but if you read the problem carefully you'll see that the links do 
not address our issue.

With the above in mind, can you please direct us towards a solution?

On Wednesday, August 26, 2020 at 12:13:31 AM UTC+3 Mary (Google Cloud 
Support) wrote:

> Hello Hadil,
>
> Yes that is correct. Since App Engine Standard the disk is read-only[1] 
> with the exception of the /tmp directory, the app.yaml file will be need 
> modified for the APP_STORAGE to reflect /tmp  as you have mentioned. If 
> these are static files that Laravel needs to retrieve you can use a Cloud 
> Storage bucket to store them. There is an open source Laravel Google Cloud 
> Storage Package[2] which can help you with this. More information can be 
> found on how to configure Laravel with the above package[3]. Please be 
> aware since this package is open source, it is not supported or endorsed by 
> GCP.
>
> [1] 
> https://cloud.google.com/appengine/docs/the-appengine-environments#comparing_high-level_features
> [2] https://github.com/Superbalist/laravel-google-cloud-storage
> [3] 
> https://stackoverflow.com/questions/57177524/laravel-how-to-access-stored-image-from-google-cloud-storage-using-php-laravel
>
> On Tuesday, August 25, 2020 at 8:02:02 AM UTC-4 hadil.cha...@mmpww.com 
> wrote:
>
>> Also, something else worth noting is that we're not sure why Laravel is 
>> trying to the write to the folder "/*workspace*/storage/framework/views/" 
>> instead of "/*tmp*/storage/framework/views/". Also, in case it's helpful 
>> to someone, below is a copy of our app.yaml (it's been configured the same 
>> way for over a year):
>>
>> APP_KEY: XXX
>> APP_URL: 'X'
>> APP_NAME: XXX
>> APP_STORAGE: /tmp
>> APP_ENV: production
>> APP_DEBUG: true
>> VIEW_COMPILED_PATH: /tmp
>>
>> On Monday, August 24, 2020 at 7:02:51 PM UTC+3 Hadil Charafeddine wrote:
>>
>>> Hello,
>>>
>>> Our team has been using App Engine Standard for this project (PHP and 
>>> Laravel 5.8.38) for over a year now without any issues with deployment. 
>>> However, a couple of weeks ago we started getting a 500 HTTP error every 
>>> time we deploy (with and without --no-promote option).
>>>
>>> When we check our logs, we find that the error is caused by:
>>> *2020/08/18 06:15:15 [error] 25#25: *2 FastCGI sent in stderr: "PHP 
>>> message: PHP Fatal error:  Uncaught ErrorException: 
>>> file_put_contents(/workspace/storage/framework/views/c1b305dfa33e081e1fc836f46439e09f829e8770.php):
>>>  
>>> failed to open stream: Read-only file system*
>>>
>>> It's very weird that we're receiving this message now even though the 
>>> project has been working fine for more than a year and we've made countless 
>>> deployments to date without this issue. Furthermore, we did not update the 
>>> configuration of the project nor did we update the Laravel version.
>>>
>>> What's even stranger is that over the past couple of weeks, 95% of the 
>>> deployments fail with 500 error and 5% succeed without issues. What's also 
>>> strange is that our team is comprised of 4 developers and 3 of us have 95% 
>>> unsuccessful deployments while one of has has 100% *successful* 
>>> deployments. There's absolutely no difference between the code the 3 of us 
>>> are trying to deploy and the code the 4th member is successfully deploying.
>>>
>>> This inconsistency is the error is baffling us. We've tried all the 
>>> solutions online we can find but nothing is working.
>>>
>>> Can anyone offer any insight on why this could be happening? Please keep 
>>> in mind that this issue started only 2 weeks ago.
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/46f9e53a-8cb3-4bdf-8e9f-015f3c09309bn%40googlegroups.com.